on 03-29-2005 3:18 PM
When I try to update SAP DB version 7.3 to Max DB version 7.5 the update exits abnomally with the following text:
current log position -1
backup log position -1
MaxDB instance update exited abnormally at Tu, Mar 29, 2005 at 09:11:07
I have set the system up for auto log backups. Any ideas why this may be happening?
Hi,
first let me ask you if your MaxDB instance is tied to either an official (i.e. full SAP) release (R/3, WAS or similar), or to a Preview Installation. In the former case, please open a OSS/CSS message for your issue, in the latter, we can continue as is.
To be able to analyze your issue in more detail, I'd need you to either send me the complete SDBUPD update logfile, or at least copy the last 20 or 30 lines from said logfile into this thread.
Kind regards,
Roland
P.S: the SDBUPD logfile normally resides in the /sapdb/data/wrk directory. Look for the matching time and date stamp.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the content of the log file I found.
CALL: SDBUPD -INSTANCE -profile APO LiveCache
STDOUT:
MaxDB INSTANCE UPDATE
STDOUT: *********************
STDOUT: starting installation Tu, Mar 29, 2005 at 09:10:54
STDOUT: operating system: Windows I386 NT 5.0 Service Pack 4
STDOUT: callers working directory: R:/Max DB 7.5.0/maxdb-server-win-32bit-i386-7_5_00_21
STDOUT: installer directory: R:/Max DB 7.5.0/maxdb-server-win-32bit-i386-7_5_00_21
MSG: InstallRegistry: space check ok: 80845020 kb on S: (90968028 kb total) available
MSG: install registry successfully locked
MSG: read 3 PACKAGES
MSG: net registry size = 53739 bytes
WRN: InstallRegistry::reserveSpace(): file >= 1024 kb
STDOUT: archive directory: R:/Max DB 7.5.0/maxdb-server-win-32bit-i386-7_5_00_21
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 "ODBC" resolved
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
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
MSG: no installation data to migrate
STDOUT: beginning to check sap db instances
STDOUT: existing instance:
STDOUT: 0: D02 "S:/sapdb/D02/DB" 7.3.0.28
STDOUT: 1: none
STDOUT: please enter instance id:
STDIN: 0
STDOUT: please enter database manager operators name:
STDIN: superdba
STDOUT: please enter database manager operators password: STDOUT:
STDIN:
STDOUT: resume broken instance check
x_server is running
got following x_server data:
version = NT/INTEL 7.3.0 Build 028-000-087-417
WRN: ".0" is not a valid release format
dbmsrv uses db_warm
dbmsrv uses db_cold
STDOUT: finding instance type...
using default instance type OLTP
instance type is OLTP
STDOUT: finding starting release...
kernel version by 'show version' 7.3.0 Build 028-000-087-540
starting release is 7.3.0 Build 028-000-087-540
STDOUT: finding migration strategy...
migration is using consistent data
from 7.3.0 Build 028-000-087-540
to 7.5.00
STDOUT: looking for running instances...
STDOUT: checking paramfile modifications...
check version of paramfile
kernel version : 7.3.0 Build 028-000-087-540
paramfile is clean
STDOUT: looking for domain user...
user profile container contains:
CONTROL
SUPERDBA
domain
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
STDOUT: database state is WARM
backup is out of date
current log position -1
backup log position -1
MSG: write 3 packages
MSG: net install registry size = 53739 bytes
MSG: wrote install registry (67199 bytes)
STDERR: MaxDB instance "D02" 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 WARM
backup is out of date
current log position -1
backup log position -1
STDERR: MaxDB instance update exited abnormally at Tu, Mar 29, 2005 at 09:11:07
MSG: install registry successfully unlocked
Hi,
the problem seems to be the following:
"
STDOUT: database state is WARM
backup is out of date
current log position -1
backup log position -1
"
Because your instance is in WARM status, new log entries have been created. The status of the instance should have been COLD in this phase of the upgrade really.
Please follow the following steps to proceed with the upgrade:
1. Move your DB into COLD mode (VERY IMPORTANT! It should stay in this mode for the duration of the below steps and beyond (until SDBUPD moves it automatically into WARM/ONLINE mode))
2. Issue the following command:
dbmcli -d <SID> -u <dbm-usr>,<pwd> util_execute migrate
Please make sure an 'OK' message appears after the above command.
3. Then, while still being in COLD mode, make a FULL DATA BACKUP (most conveniently done using the Database Manager GUI).
After the above steps, you should have a full data backup that could be imported into MaxDB 7.5 database (by following a certain procedure).
4. Keep the instance in COLD mode and proceed with calling SDBUPD. The upgrade/migration should work this time around.
Hope that helps.
Regards,
Roland
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.