MaxDB 7.6.04.11 upgrade to 7.8.02.23 HP-UX DBUPDATE.SH prompts TERM = (hp)

[Former Member]

Trying to upgrade MaxDB 7.6.04.11 for ECC5 with 640_EX2 kernel on HP-UX PA-RISC 11.23 to MaxDB 7.8.02.23 but when logged on as root and running DBUPDATE.SH initally get expected prompts, but then get line showing:

TERM = (hp)

and I don't know what to enter (have tried hp and vt220 - default for root seems to be xterm) but I try 2 different values and then get thrown back to command prompt. Have tried setting TERM=vt220;export TERM but no success. Please can anyone help me work out what is causing this variable to be prompted for while I'm running DBUPDATE.SH ? Here is the interaction I get with DBUPDATE.SH

/usr/sap/MDB78DVD/51041558_14/RDBMS_MaxDB_7.8.01.14___7.8.02.23/DATA_UNITS/MAXDB_HPUX_PARISC:# ./DBUPDATE.SH

INFORMATION : This program upgrades the SAP MaxDB database instance

from at least version >= 7.5

to SAP MaxDB version 7.8.

CAUTION:

The upgrade phase "migrate catalog"

will need a long operating time.

Don't cancel the execution of the upgrade.

Otherwise the risk of data leakage exists!

Note:

With version 7.8,

the Isolated Installation is introduced.

Upgrade strategy:

In-Place Upgrade with SDBUPD

To prepare for the upgrade you need a data backup

as described in the upgrade guide:

'Upgrade to SAP MaxDB version 7.8' !

You can find this on SAP Service Marketplace at:

http://service.sap.com/instguides -> Database Upgrades -> MaxDB

Do you want to continue the upgrade [Y] : Y

Check installation of C++ runtime

...execution 16:12:54

OK

IndepProgPath : /sapdb/programs

IndepDataPath : /sapdb/data

Please enter SAP MaxDB Name [SID] : NDV

Please enter SAP System Name [SID] : NDV

Please enter DBM User Name [control] : control

Please enter DBM User Password :

INSTROOT : /sapdb/NDV/db

Authorization successful

DB KERNEL : 64-BIT

DB VERSION : 7.6.04 Build 11

Database instance version supported

PrivateDataPath : NO

Check availability of SAP users

...execution 16:13:10

SAP System Administrator : ndvadm

SAP Database Administrator : sqdndv

OK

TERM = (hp)

<Enter> with nothing, or entering value, just gets thrown back to command prompt after 2 goes.

Many Thanks,

James.

[former_member188883]

Hi James,

You shall enter TERM = vt100.

This is basically the terminal settings for the user with which u have logged in.

You can hard code this value in the .login and .profile files of that user.

Regards,

Deepak Kori

[Former Member]

Hello deepakkori,

Thank you very much for your response. Your suggestion of editing the .login or .profile was very helpful. /home/ndvadm/.login had in it some code to prompt for $TERM and that seemed to be appearing when running DBUPDATE.SH because at that point it seems to log on with ndvadm. I edited .login and added setenv statements to set TERM and DBTERM to vt220. However, it's now showing an error about the user/password for a user. Output is:

clyde:/usr/sap/MDB78DVD/51041558_14/RDBMS_MaxDB_7.8.01.14___7.8.02.23/DATA_UNITS/MAXDB_HPUX_PARISC:# ./DBUPDATE.SH

INFORMATION : This program upgrades the SAP MaxDB database instance

from at least version >= 7.5

to SAP MaxDB version 7.8.

CAUTION:

The upgrade phase "migrate catalog"

will need a long operating time.

Don't cancel the execution of the upgrade.

Otherwise the risk of data leakage exists!

Note:

With version 7.8,

the Isolated Installation is introduced.

Upgrade strategy:

In-Place Upgrade with SDBUPD

To prepare for the upgrade you need a data backup

as described in the upgrade guide:

'Upgrade to SAP MaxDB version 7.8' !

You can find this on SAP Service Marketplace at:

http://service.sap.com/instguides -> Database Upgrades -> MaxDB

Do you want to continue the upgrade [Y] : Y

Check installation of C++ runtime

...execution 00:37:45

OK

IndepProgPath : /sapdb/programs

IndepDataPath : /sapdb/data

Please enter SAP MaxDB Name [SID] : NDV

Please enter SAP System Name [SID] : NDV

Please enter DBM User Name [control] : control

Please enter DBM User Password :

INSTROOT : /sapdb/NDV/db

Authorization successful

DB KERNEL : 64-BIT

DB VERSION : 7.6.04 Build 11

Database instance version supported

PrivateDataPath : NO

Check availability of SAP users

...execution 00:37:57

SAP System Administrator : ndvadm

SAP Database Administrator : sqdndv

OK

SAP VERSION : -4001,Unknown user name/password combination in operational state ADMIN

ERROR: Upgrade tool not found or not executable !

--> If SAP MaxDB DVD has been copied to disk

--> check the existence and authorizations of file:

--> /usr/sap/MDB78DVD/51041558_14/RDBMS_MaxDB_7.8.01.14___7.8.02.23/DATA_UNITS/MAXDB_HPUX_PARISC/../MAXDB_HPUX_PARISC/SDBUPD

--> Otherwise, please contact the SAP support team.

clyde:/usr/sap/MDB78DVD/51041558_14/RDBMS_MaxDB_7.8.01.14___7.8.02.23/DATA_UNITS/MAXDB_HPUX_PARISC:#

This is not a java system, just ABAP, so the info in note 1353266 saying this can be ignored in a java system is not applicable here. I'm not sure though which user it's complaining about or why. Any other suggestions very welcome.

Thanks,

James.

[Former Member]

I just wanted to add a bit more information about the history of the

system I'm upgrading MaxDB on. It is a system copy (backup/restore)

from the QA system, so has had the following done to it:

Note 129352 c:

dbmcli -d <database_name> -u <dbm_user>,<password> load_systab -u

<sysdba_user>,<sysdba_user_password>

dbmcli -d NDV -u control,CONTROL load_systab -u superdba,admin

Note 129352 d:

dbmcli -d <NEWSID> -u control,control -uSQL superdba,admin

sql_execute rename user SAP<SID> to SAP<NEWSID>

dbmcli -d NDV -u control,CONTROL -uSQL superdba,admin sql_execute

rename user SAPNQA to SAPNDV

Note 129352 e:

Run SQL to clean up CCMS

Actual runs of above:

clyde:ndvadm 540> dbmcli -d NDV -u control,CONTROL load_systab -u

superdba,admin

OK

0,OK: everything works fine

0,/sapdb/NDV/db/bin/x_python /sapdb/NDV/db/env/lsystab.py -

R /sapdb/NDV/db -d NDV -u superdba,*

Removing obsolete objects

Installing Loader tables

Installing messages and help

Installing SYSDBA tables

Installing comments for SYSDBA tables

Installing precompiler tables

Installing system tables for R3 backup information

Installing ODBC tables

Installing system tables for ORACLE (V7) mode

Installing data dictionary tables and views

Installing synonyms for oracle system tables

Installing comments on oracle sytem tables

Installing tables for WebAgent

Installing tables for Repository (WebDAV)

Installing DOMAIN tables

Installing comments for DOMAIN tables

Installing Views as replacement for SHOWs

Installing Database Manager tables

Installing SYSINFO tables

Installing comments for SYSINFO tables

Installing support for UDE (User Defined Extensions)

Installing tables for JDBC Database Metadata

Installing tables for SQLDBC Database Metadata

Installing additional triggers

Installing tables for DBAnalyzer

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

Installation successfully finished

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

clyde:ndvadm 541>

clyde:ndvadm 541> dbmcli -d NDV -u control,CONTROL -uSQL superdba,admin

sql_execute rename user SAPNQA to SAPNDV

OK

clyde:ndvadm 542>

I also used xuser to set passwords. Maybe I got something wrong in:

Note 39439 says to do following for Norco release of SAP:

xuser -U DEFAULT -u SAPNDV,sap -d NDV -n clyde -S SAPR3 -t 0 -I 0 set

xuser -U c -u CONTROL,CONTROL -d NDV -n clyde -S INTERNAL set

xuser -U w -u SUPERDBA,admin -d NDV -n clyde -S INTERNAL set

Maybe I got something wrong above ?

Cheers,

James.

[Former Member]

The problem is solved. It was not a permission error in the end. The file didn't exist. The copy of the upgrade DVD which I had uploaded was incomplete. Sorry for confusion. However, I hope I can at least add something to this:

It is possible to upgrade 7.6.04.11 to 7.8.02.23 on a host which has more than one SAP system on it (4 databases in this case) and only upgrade one database at a time. I have upgraded dev and QA still starts with 7.6.04.11successfully !

Thanks for support,

James.