> How can I check what is the exact version of my SAPDB setup? If mine is older than
>the latest
d:\ >dbmcli -u <username>,<password> -d <dbname> sql_execute select * from versions
OK
END
'Kernel 7.3.0 Build 033-000-000-000';'NT/INTEL 7.3.0 Build 033-000-000-000'
==================
> how can I upgrade without uninstalling & reinstalling the entire SAP-R/3
> application (maybe this question is slightly off-topic, but I am giving it a try...)?
!!!!! IMPORTANT: Do not use these steps to upgrade from any 7.3 release to 7.4 !!!!!
Hint: you can't download from http://service.sap.com/PATCHES, only from
http://www.sapdb.org/sap_db_downloads.htm
Symptom
This note describes the importing of a SAP DB patch for the version
7.3.0 >= B24.From this build the SAP DB patches are provided in the SAP
Software Center.
To install a liveCache patch refer to note 379051 or 533076 or 498012.
Additional key words
Upgrade, new database version, version, database release, Release, patch
Cause and prerequisites
When importing a version 7.3.0 you must already be using a SAP DB 7.3.0
version.
Caution: this note does NOT describe the migration
o from SAP DB 6.2 (via 7.2.5) to SAP DB 7.3
o from SAP DB 7.x with (x < 3) to SAP DB 7.3
To carry out the migration to 7.2.4, you must proceed as described in
note 339673.
The migration to 7.2.5 is described in note 382741.
A direct migration from 6.2.10 to 7.3 is not possible, migrate through
7.2.5 and then to 7.3.0 in accordance with note 397652.
The CDs mentioned there may have to be ordered separately.
You are recommended to change immediately to the highest possible
version 7.x. The release is described in the corresponding notes.
No 32-bit version may be installed above an existing 64-bit version!
Solution
General:
Set up the recovery ability of the database before you import the
database patch. If you cannot execute a 'SAVE DATA FOR MIGRATION',
ensure that all changes of your dataset were saved since the last 'SAVE
DATA' (SAVE PAGES / SAVE LOG).
N T
1. Preparation:
==================
o Stop the R/3 System.
o Stop the database before importing the software.(Mode "Offline" -
do NOT use the option "Quick" during the shutdown.If the DBMCLI
is used, use the command db_offline!)
If other SAP DB instances are also running on this host, these
must be stopped too.
o Stop the server for remote SQL ('x_server stop').
o Terminate all DBMGUIs and all DBMCLI sessions.
o Save the database software directory: <Drive>:\sapdb
2. Import the new release:
=================================
o Change into a temporary directory (for example C:\temp)
o Log on to the SAP Software Center:
http://service.sap.com/PATCHES
o Transfer the file
SAPDB<Build-GUID>.SAR
of the desired release from the following path:
OLTP and content server version:
-> SAP DB
-> SAP DB OLTP
-> SAP DB <version> OLTP
-> NT/I386
BW version:
-> SAP DB
-> SAP DB OLAP
-> SAP DB <version> OLAP
-> NT/I386
You will also find the unpacking tool SAPCAR in the SAP Software
Center, as described in note 212876.
o Log off from the SAP Software Center.
o Unpack the SAR package in the temporary directory:
SAPCAR -xvf <file name>.SAR
o Change into the created directory
sapdb-server-win-32bit-i386-<Build>
o You can then call the tool SDBINST at the command prompt.If
SDBINST is started via the Explorer, any errors that have
occurred may not be displayed.First the 'independent' package is
installed, the following entries are required:
- Display of installation data, 'Are these values correct?(y/n)'
-> Check data and confirm as required
After the unpacking of this software package the installation of
the 'dependent' package follows automatically.The following
entries are required:
- Display of a list of the existing installations, 'update
existing installation (y/n):' -> y
- 'please enter installation id:'-> enter the number that is
displayed before the corresponding installation
- Display of installation data, 'Are these values correct?(y/n)'
-> Check data and confirm as required
o The database software is now installed.
After the unpacker has displayed the message that the installation was
successful, you can continue with the following steps.
3. Follow-up:
===================
o Call xtcpupd at the input prompt and select
Remote SQL/enable TCP/IP support
If xtcpupd reports that an entry in the registry is not correct
(sqltcp.dll), change the corresponding registry entry as follows:
old:
HKLM\Software\SAP\SAP DBTech\DLLs -> TCPIP=sqltcp.dll
new:
HKLM\Software\SAP\SAP DBTech\DLLs -> TCPIP=sqltcp1.dll
xtcpupd can then be called.
o Enter the following commands at the input prompt:
- x_server start
- dbmcli -d <DB Name> -u <dbm user>,<dbm user password>
(for example, dbmcli -d LC1 -u control,control)
dbmcli on <DB Name>->db_register
dbmcli on <DB Name>->param_checkall
dbmcli on <DB Name>->db_warm
dbmcli on <DB Name>->exit
- dbmcli -d <DB Name> -u <dba user>,<dba user password>
(for example, dbmcli -d LC1 -u superdba,admin)
dbmcli on <DB Name>->load_systab -ud <domain password>
dbmcli on <DB Name>->exit
o The following command must also be executed on BW systems:
- lcinit <DB Name> register
This concludes the importing of the new version.
After you load the system tables, shut down the database and then start
the R/3 System and the database with the SAP service manager.
> On another topic, I have recently downloaded the document "repmgr_73eng.pdf"
> (reference for Replication Manager, Rel.7.3). I have observed that many links in the
> document are broken, i.e., in many cases, they are far away from where they are
>supposed to
> be and this makes it very difficult to read the document. Is there an updated
>(correct)
> version of this document? Is it because I am using version 5.1 of Acrobat Reader
>software -
> should I downgrade it?
Links across documents are not handled very well by the PDF generation software.
Download the documentation in HTML
(ftp://ftp.sap.com/pub/sapdb/7.3/sapdb-htmldoc-7.3.tgz) instead.
Daniel Dittmar
--
Daniel Dittmar
SAP DB, SAP Labs Berlin
[EMAIL PROTECTED]
http://www.sapdb.org/
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
