"Table VSEOPARENT is not in the database" after SolMan system copy to x64

[Former Member]

Hi SDNners,

We've just completed a system copy of our SolMan 3.1 system onto a new

(Xeon x64 based) server. This system copy is part of the process of

moving SolMan 3.1 from an old server onto 64bit hardware and then

upgrading it to SolMan v4 and Oracle 10G.

Although the system appears to start properly in the MMC, we are unable

to log into the system through SAPGUI - we get a SYNTAX_ERROR window

instead of a logon screen.

I've checked the SysLog from within the MMC and noticed a number of

errors stating:

Database: Table VSEOPARENT is not in the database

Database: Table VSEOIFIMPL is not in the database

Database: Table VSEOIFCOMP is not in the database

I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and

it confirmed that the table didn't exist. I then ran the same command

on the source SolMan system and it showed that VSEOPARENT DID exist. I

don't understand how these VSEO* tables could have gone missing between

the source and target systems.

I've searched OSS for VSEO* and cannot find anything. Please help!

Thanks,

Arwel.

[former_member185954]

Hi Anwel,

This sure looks strange, anyways I have 2 questions for you

1.Did you do any SPDD, SPAU adjustments during upgrade ?

2.Are you using the latest SAP GUI ?

Regards,

Siddhesh

[Former Member]

Hi Siddhesh,

We've not got to the actual upgrade phase yet; we've run a system copy of the source SolMan 3.1 system and cannot get it to start on the target server. Oracle is working fine, but SolMan 3.1 does not start properly, stating missing VSEO tables. It's certainly something I've never seen before, despite running many system copies in the past.

I can only guess that it's something to do with the source system running on ancient x86 hardware under Windows 2000, whilst the new system runs on x86-64 Xeon hardware under Windows Server 2003 x64. Has anyone else experienced similar problems in migrating 32bit systems to x64?

Thanks,

Arwel.

[former_member185954]

Hi Arwel,

I doubt that could be the case, processors has nothing to do with Database tables, i am sure there could be some kind of missed step or configuration steps or something else.

Please check your steps again and if required raise an OSS message to SAP to actively resolve this.

Regards,

Siddhesh

[Former Member]

Arwel,

Did you solve this problem? I am currently migrating ECC 5.0 from AIX/ORACLE to WIN2003/MSSQL 2005 and facing same issue...

Simultaneously, I have migrate another ECC 5.0 from LINUX/ORACLE to WIN2003/MSSQL but didnt face any problem despite the table wasn't exists in that system too.

I would appreciate if you can share the solution.

Regards,

Mamadi.

kapasi.mamadi@gmail.com

[Former Member]

We have 640 kernel, ECC 5.0 and BASIS patch 23.

For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.

It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.

I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.

Using migration monitor I did re-export and re-import and this time all views are imported in target.

Regards,

Mamadi.