11.6.11

SAP Note 25969 - Additional Info: Upgrading to 3.0A INFORMIX

Symptom:

Errors in the guidelines or problems during the upgrade which only occurred after creating the guidelines.

Additional key words
Cause and prerequisites

*

Solution
*******************************************************************
This note only contains INFORMIX-specific problems!!!
*******************************************************************

The topics are Date of last change
============== ===================
0/ Space requirements in Dbspaces
I/ Actions before Upgrading to 3.0A
II/ Errors in the Guidelines
III/ Problems in the Upgrade Phases
IV/ Problems after Upgrading to 3.0A

**********************************************************************
0/ Space requirements in Dbspaces
**********************************************************************

The table below gives the space requirements for individual dbspaces:

Space Required (KB)
(according to starting release)
Dbspace 2.2D/E/F 3.0FCS
====================================================
rootdbs 33 11
psappool 243 77
psapbtab 110 66
psapprot 6 6
psapstab 275 220
psapddic - 28
psapes30a 2500 2500 -> new Dbspace
psapel30a 390 390 -> new Dbspace
In order to create the new dbspaces (psapes30a and psapel30a), you need
either ON monitor (more information about this can be found in the
INFORMIX manual "INFORMIX-OnLine Dynamic Server, Administrator's Guide")
or use the onspaces command:
"onspaces -c -d -p -o -s "

**********************************************************************
I/ Actions before Upgrading to 3.0A
**********************************************************************

When executing the script ALTERSYS.SH (see upgrade guidelines), the SAP system must be shut down.

----------------------------------------------------------------------

To prepare a 3.0A upgrade, there is a report (RSATAF03) which, determines the additional time and space required, depending on the application data volume.
This is especially important for systems into which large datasets have already been copied.

The report is stored on the CD 'SAP Kernel' in the subdirectory DBTOOLS and can be imported as follows:

- Mount the CD 'SAP Kernel'
- Import the report with R3trans:
"R3trans -i //DBTOOLS/RSATAF03"

The report RSATAF03 can be executed with transaction SE38. So that the report can deliver useful results, you must perform an 'update statistics medium' before executing the report.

See also note 27943.

**********************************************************************
II/ Errors in the Guidelines
**********************************************************************

**********************************************************************
III/ Problems in the Upgrade Phases
**********************************************************************

In the phase MAIN30A, errors with the following error message in log MAIN30.ELG can arise:

SQL error "-750" during "" access: "INF750 Invalid
distribution format found for "

In this message,
stands for a table and for a field of
this table.
In this case, carry out the following SQL statement as user 'informix' for each table/field given:

"update statistics low for
() drop distributions;'

Replace
or with the given table or field name.

Then you can continue the upgrade with 'repeat'.

**********************************************************************
IV/ Problems after Upgrading to 3.0
**********************************************************************

Creation of database-specific objects

o Shell script D010LINF.SH

With the shell script D010LINF.SH, additional informix-specific
indexes/constraints for the table D010LINF are created. The script
is in the directory DBTOOLS on the 3.0A Kernel CD. It is also to
be found on sapservX in directory
/general/3rdparty/informix/upgrade as D010LINF.SH.34045.

Start the script as follows:
"su - informix"
"/DBTOOLS/D010LINF.SH

WARNING: If the SAP system is running when the script is started,
ISAM error -106 can occur: "non-exclusive access."
In this case, you must bring down the SAP system
("stopsap r3") and re-run the script.

o Report SINDXINF

After the upgrade, execute the program SINDXINF.
The report creates database-specific objects (e.g. indexes).

You must make sure you have imported the latest version of the report
into your system. You will find the R3trans file on the 3.0A Kernel
CD in directory DBTOOLS. It is also to be found on sapservX in
directory /general/3rdparty/informix/ddic as 'SINDXINF.29751'.

Import the report as follows:
"su - adm"
"R3trans -i /DBTOOLS/SINDXINF"

Now you should generate and start the report SINDXINF with the
transaction SE38 (NOT as user DDIC!)

========================================================================

Access rights for SAPDBA
========================
If you wish to use SAPDBA, you will need to change the access rights
for the program /usr/sap//SYS/exe/run/sapdba as follows:
o "su root"
o "cd /usr/sap//SYS/exe/run"
o "chown informix sapdba"
o "chgrp informix sapdba"
o "chmod 6755 sapdba"

No comments:

Post a Comment