SAP Basis Tech Supports

Problems w/ database links during the System Switch Upgrade

June 29, 2009 at 3:00 am

[create database] [database] [database desktop] [link] [PARMVNT_SHD] [problems] [switch] [synonym] [system] [upgrade]

ByD: MaxDB Log Files to analyze Database ProblemsSymptom This note describes the needed MaxDB database log files...
Old database scan tool: RSCPSRCHSymptom The database scan tools RSCPSRCH and RSCPUPDT do not...
System requirements HP-UX PA-RISC liveCache/MaxDB 7.5 to 7.7Symptom No symptom has been assigned to this note. Other...
Overview note of DB analyzer problemsSymptom This note is an overview note about problems with...
Bad indexes after software upgrade 7.3.00 Build 27Symptom B*TREE BAD INDEX 865672 (ROOT) in the knldiag.err since...
DB2 z/OS: Overview of transports and correctionsSymptom This note contains an overview of all transports and...
640PC Edition May 2008:Installation IBM DB2 on z/OSSymptom This SAP Note is valid for the following releases:...
DB2-z/OS: Upgrade to SAP NW AS 7.1 and higher – free spaceSymptom Disk space required for an upgrade to SAP Basis...

Symptom

What must I bear in mind during the system switch upgrade if I am using “database links” as described in Note 25383?

Other terms

Database link, synonym, PARMVNT_SHD, system switch upgrade

Reason and Prerequisites

Errors will occur during the system switch upgrade if you use the “database links” defined in the ABAP Dictionary.
Since the objects in the ABAP dictionary are defined as tables, but were created on the database as synonyms, the existence check determines that the objects do not exist on the database. During the upgrade, DROP/CREATE statements are calculated for the tables to be executed in the phase PARMVNT_SHD. The system then issues the following error message:

Oracle:
ORA-955 name is already used by an existing objectDB2 for z/OS:
SQL-error “-601-[IBM][CLI Driver][DB2]SQL0601N The name of the object to be created is identical to the existing name “SAPR3.tabname” of type “ALIAS”.SQL

because the objects are already defined as synonyms.

Solution

After the error occurs, log on as the usual SAP database user for the system and update the database as follows:
update “DDXTT~” set modeflag = ‘A’ where tabname = ‘table1′;
Instead of table1, use the table name that was named in the error message ORA-955 or SQL-error -601.
Then use ‘repeat’ to repeat the phase PARMVNT_SHD.