SAP Note 26471 - Additional Info: Upgrading to 3.0A ORACLE

Symptom:

Errors in the guide or in the upgrade procedure that did not come to light until after the guide was produced.

Solution
Important: This note is to be maintained by the Software Logistics
department only. This applies to both German and English
versions of the note. Please do not make any entries in
the note yourself. Forward any changes you require to user
D019144.
*******************************************************************
This note contains only ORACLE-specific problems!!!
********************************************************************

Topics Date of last change
================= =====================
I/ Other information 09/NOV/95 d021311
II/ Errors on the CD 18/OCT/95 d019983
III/ Errors in the Guides
IV/ Problems during the ORACLE Upgrade 17/OCT/95 c1399114
V/ Problems with PREPARE 27/OCT/95 d021311
VI/ Probl. in the Individual SAP Upgrade Phases
VII/ Problems after Upgrading to 3.0A 26/OCT/95 d019144

--------------------------< d000706 14/NOV/95 >------------------------
CAUTION:
In start release 2.2*, the sources of the customer's GUI interfaces
(menues, buttons, stati, ...) are missing after upgrading to 3.0A.

If you have your own GUI interfaces, it is essential that you read
Note 28819 b e f o r e beginning upgrading. In this note, you will
find solutions for the problem:
* If you have a remote connection, it describes how you can get a
corrected version of R3trans.
* If you have no remote connection, it describes how you can save the
sources before upgrading.
**********************************************************************
I/ Other information
**********************************************************************
---------------------------------------------------
For NT under Oracle:
In the 3.0A kernel CD, directory \NT\ORACLE has a patch containing an
upgrade to Oracle 7.1.3.3.12.
The patch can be imported as follows:
Create a temporary directory, start a DOS box and change to the
temporary directory.
Unpack the patch with:

CAR -XVF :\NT\ORACLE\BG306043.CAR

Execute the programs bg306043_1.exe.exe and bg306043_2.exe.exe, which
unpack themselves, and then proceed as described in file README.TXT.

**********************************************************************
II/ Errors on the CD
**********************************************************************
---------------------------------------------------
Only if a ORACLE version 7.0.x was active before the ORACLE upgrade
to 7.1.6:
Problem:
The program change_init.ora is missing on the CD.
Therefore you cannot start this program as described in the Upgrade
Guide in Appendix G under "Activities after Upgrading".
Solution:
Manually delete the parameter "init_sql_files" from the file
$ORACLE_HOME\dbs\init< SID>.ora.

**********************************************************************
III/ Errors in the Guides
**********************************************************************

**********************************************************************
IV/ Problems during the ORACLE Ugrade
**********************************************************************
--------------------------------------------------
SINIX only:
Symptom:
ORA7404 and database crash with ORACLE 7.1.6 on SINIX
Cause:
The database was started with several Database Writers
Solution:
Change the init.ora as follows:
db_writers = 1

**********************************************************************
V/ Problems with PREPARE
**********************************************************************
------------------------< D021311 27/OCT/95 >------------------------
Only for upgrading from FCS to 3.0A:
The freespace required for tablespace PSAPSTABI specified by
PREPARE (SPACECHK phase) is too small!

Please extend the tablepace by 10 MB more than required or by 10MB,
if no extension is specified.

**********************************************************************
VI/ Problems in the Individual Upgrade Phases
**********************************************************************

**********************************************************************
VII/ Problems after Upgrading to 3.0 A
**********************************************************************
------------------------< d019144 26/OCT/95 >--------------------------
Please note that the tablespaces PSAPES300D and PSAPEL300D may NOT be
empty after the upgrade from 3.0 FCS to 3.0A. You cannot therefore
delete the tablespaces as described in the guide (chapter 4,
Subsequent processing activities for the database).

First check whether the tablespaces still contain tables:
1. Log on to the database with sqlplus.
2. Enter the following SQL commands:

SELECT SEGMENT_NAME, SEGMENT_TYPE FROM DBA_SEGMENTS
WHERE TABLESPACE_NAME = 'PSAPES300D';

SELECT SEGMENT_NAME, SEGMENT_TYPE FROM DBA_SEGMENTS
WHERE TABLESPACE_NAME = 'PSAPEL300D';

If table names are displayed for one of the two commands, for example
'T100O TABLE' or 'EUGUITEXT TABLE', you will have to move these tables
before deleting the tablespaces.

To do this use program sapdba (Version 3.0A) as follows:
1. Call sapdba as user ora at operating system level.
2. Select Reorganization --> Reorganize table or index.
3. Enter for example "T1000" or "EUGUITEXT" for the table name.
Under the menu option "Target tablespace" enter the target
tablespace "PSAPDDICD".

Afterwards you can delete the four PSAPE*300 tablespaces as described
in the guide, with the following exception:
Replace the four drop commands with:
drop tablespace PSAPES300D;
drop tablespace PSAPES300I;
drop tablespace PSAPEL300D;
drop tablespace PSAPEL300I;

---------------------------------------------------
To avoid problems when backing up, the following new parameters have to
be inserted into the init.sap profile:

- cpio_in_flags = -iduvB defines the cpio flags for reading
from tape
Caution: If you have changed the standard value for parameter
cpio_flags (= -ovB ), you must adjust the new parameters
appropriately.
Example: cpio_flags = "-ov -C 16384"
cpio_in_flags = "-iv -C 16384"

- uncompress_cmd = "uncompress - c $ > $" defines the uncompress
command
Caution: under Windows NT this parameter has a different value:
uncompress_cmd =
"\\%SAPLOCALHOST%\sapmnt\\SYS\exe\run\uncompress -c $ > $"
(line break is not necessary)
- tape_pos_cmd = "mt -f $ fsf $" defines the tape
positioning command

Caution: under HP-UX the parameter has a different value:
tape_pos_cmd = "mt -t $ fsf $"

under AIX the parameter has a different value:
tape_pos_cmd = "tctl -f $ fsf ape_pos_cmd = "tctl -f $ fsf
$"

------------------------< C1016615 15/NOV/95 >------------------------
SINIX only:
When you click on "CPU" after starting SM50/SM51, the "CPU" time used is
displayed. However many defunct processes, which are generated like
work processes, remain at the operating system level so that after
clicking several times the SINIX resource "MAXUP" is used up.
The only solution at present is:

- not to click on "CPU"
- to afterwards cancel the dialog work process without the core
- restart R/3