Unknown table name:INFO_STATE after upgrading from 7.5 to 7.6

[former_member182374]

Hi all,

I upgraded my MaxDB from version 7.5 Build 25 to 7.6 Build 18.

I got "upgraded successfully" on the end of the process, but the dbupdate.bat hangs on the "loading system tables..." step after I get the "upgraded successfully" message.

I tried to load system tables by

DBMGUI -- Configuration -> Upgrade System Tables

and

DBMCLI -- dbmcli -d <SID> -u <dbm-user>,<pwd> load_systab -u <dba-user>,<pwd> -ud DOMAIN

with no success - the process hang and there is no error message.

How to fix this?

Thanks,

Omri

[former_member182374]

I will how it goes with SAP support

Omri

[former_member229109]

Hello Omri,

1) Are you SAP customer?

If you are SAP customer => Did you already create the SAP OSS message on this issue?

2) Please run the following commands & post the outputs in the thread::

dbmcli inst_enum

dbmcli db_enum

xinstinfo <SID>

x_cons <SID> sow active

Please check the errors in the knldiag file.

Thank you and best regards, Natalia Khlopina

[former_member182374]

Hi Natalia,

Thanks for the help.

By using 'xcons' I realized that my log is full.

Clearing the log and running load_systab solved the problem.

Now I have a new problem:

My DB is a part of a content server.

I have two schemes: DMS & DMC (DMS is data itself, DMC is cache).

DMS was upgraded successfully.

When running upgrade for DMC I get error message (see log).

What could be the problem?

Log file:

STDOUT:

starting preparing phase of package Loader 7.6.00.18 32 bit

STDOUT: -

---

MSG: update test: release equal or higher than installed

MSG: update from "7.6.0.18" to "7.6.00.18" allowed

STDOUT: update release check... ok

magic test mode: NOBIT

MSG: magic test: ok

STDOUT: update binary magic check... ok

STDOUT: checking interferences to other packages... STDOUT: ok

STDOUT: collecting data finished:

STDOUT: loader path: C:/sapdb/programs

STDOUT: start extraction test run of "D:/source/MaxDB76/MAXDB_WINDOWS_I386/SDBLD.TGZ"

STDOUT:

package Loader successfully checked

STDOUT:

starting preparing phase of package Messages MSG 0.3017

STDOUT: -

---

<b>WRN: "" is not a valid release format

WRN: "" is not a valid release format

STDERR: needed minimal version (0.0.0.1) of installed package () not reached

STDERR: MaxDB instance update exited abnormally at Su, Feb 17, 2008 at 10:06:43</b>

MSG: packagedata of package Base not changed

MSG: packagedata of package PCR 7104 not changed

MSG: packagedata of package PCR 7300 not changed

MSG: packagedata of package PCR 7301 not changed

MSG: packagedata of package PCR 7403 not changed

MSG: packagedata of package ODBC not changed

MSG: packagedata of package DB Analyzer not changed

MSG: packagedata of package Database Connectivity not changed

MSG: packagedata of package SQLDBC 7600 not changed

MSG: packagedata of package JDBC not changed

MSG: packagedata of package Server Utilities not changed

MSG: packagedata of package Database Kernel not changed

MSG: packagedata of package Redist Python not changed

MSG: packagedata of package Loader not changed

MSG: packagedata of package Messages not changed

MSG: install registry successfully unlocked

Thanks,

Omri

[former_member229109]

Hello Omri,

I saw that you aleady created the OSS message 141091/2008,

where you reported the last issue of the database upgrade with two

schemas. Please follow the OSS message to resolve this issue.

Please read this thread: MaxDB/liveCache Forum: target audience and relevant support.

< >

Thank you and best regards, Natalia Khlopina

[former_member229109]

Hello Omri,

You have two database instances DMS & DMC on one server.

Brief summary of the solutions for the problems reported in this thread::

A) After the upgrade of DMS instance the load system tables failed due the

LOG_FULL issue. The LOG_FULL was resolved => the system tables were reloaded.

PS: Please review the SAP notes ::

869267 FAQ: MaxDB LOG area

767598 Available documentation

B) The upgrade of the database DMC failed due the unresolved check for the

database software package Messages MSG 0.3017.

After the package Messages was uninstalled, the upgrade of the database

instance DMC was done without problems.

PS: The database version '7.6.0.18' is quit old, please update the database to the

newest released database 7.6 patch to avoid the known problems fixed in the new

release, see the SAP Note No. 1020175 concerning questions to apply the patch.

Thank you and best regards, Natalia Khlopina

[former_member182374]

Thanks for the help Natalia in both forum & OSS message.

One more thing I would like to add:

It's important to upgrade the GUI tool to the same Major/Minor version as the DB itself.

I couldn't see that the log is full by using GUI version 7.5 with MaxDB 7.6 (I found it out by using 'xcons').

However, when I upgraded the GUI too to version to 7.6 I could see it.

Omri