cancel
Showing results for 
Search instead for 
Did you mean: 

shadow system problem

Former Member
0 Kudos

Hello,

I have the following problem-

history

migrated database from mssql 2000 to 2005 (ran the copy tools and all)

BW 3.1 running with 640 kernel

started upgrade

everything went fine up to start of shadow system:

dev trace:

C np:(local) connection used on BEBRUBW04

C CopyLocalParameters: dbuser is 'pbd_shd'

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C Provider Release:9.00.3042.00

C Using Provider SQLNCLI

C OpenOledbConnection: MARS property was set successfully.

C CheckCodepageType: line 24644. hr: 0x80040e37 Invalid object name 'DBPROPERTIES'.

C sloledb.cpp [CheckCodepageType,line 24644]: Error/Message: (err 208, sev 16), Invalid object name 'DBPROPERTIES'.

C Procname: [CheckCodepageType -- no proc]

C Cache sizes: header 88 bytes, 20000 names (28160000 bytes), 500 dynamic statements (2756000 bytes), total 30916088 bytes

C Using shared procedure name cache BEBRUBW04_PBDPBD_PBD_SHD_MEM initialized by another process.

C Connected to db server : [BEBRUBW04] server_used : [np:(local)], dbname: PBD, dbuser: pbd

C pn_id:BEBRUBW04_PBDPBD_PBD_SHD...

shadow system just could not make the connection to the db

anyone knows a reason why ? - I checked the sid_shd user, all seemed ok

thanks

Paul

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I had to restart the upgrade...

what I noticed is that sid_shd user got a grant stored procedure (read version) added to its profile this time which probably allowed it to read the SVERS and DBPROPERTIES

so, all went fine then...

Paul

Former Member
0 Kudos

No, collation is ok, did all migrations beforehand

Former Member
0 Kudos

Hi Paul,

are you sure that tab DBPROPERTIES is in the right schema (pbd)? Error "Invalid object name" points in that direction.

Sven

Former Member
0 Kudos

Hi,

This problem is for BIN collation.

1. You have to convert from BIN (MS SQL Server 2000) to BIN2 (MS SQL Server 2005 ) collation.

2. Check first db properties in MS SQL Server for Collation.

Regards,

Srini Nookala