Prepare Phase INIT_PRE

[Former Member]

Hi,

We are upgrading our NetWeave 04 (BW 3.5) to BI 7.0.

When running prepare phase we are getting following error during

INIT_PRE phase.

Cannot open logfile for read F:\usr\sap\put\log\MSSCONCHECK.log

In the log directory in MSSCONCHECK.OUT I cansee following error

message

SAPup> Starting subprocess osql with id 2804 at 20081001171845

EXECUTING osql -S AUS-SAPBWDB1 -E -d -i

F:\usr\sap\put\bin\MSSCONCHECK.SQL -o

F:\usr\sap\put\log\MSSCONCHECK.LOG -h-1 "-w 100" -n

'osql' is not recognized as an internal or external command,

operable program or batch file.

Process with ID 3048 terminated with status 1

I have checked the login details in database and sidadm has got default

database and sys admin rights.

FYI, Application server: aus-sapbwapp1

Database Server: aus-sapbwdb1

Database: BWQ

Enviornment Variables are set as below in both servers:

MSSQL_SERVER: AUS-SAPBWDB1\BWQ -- Named Instance

MSSQL_DBNAME: BWQ

Also profile parameters as below

SAPDBHOST = AUS-SAPBWDB1

dbms/type = mss

dbs/mss/server = AUS-SAPBWDB1\BWQ

dbs/mss/dbname = BWQ

Please advise what we are missing

Thanks

Santosh

[Former Member]

Hi,

The OSQL file is normally located in the \binn directory. Check if it is there and try running the command osql -S AUS-SAPBWDB1 -E from that directory. Does this connect to the SQL Server?

Cheers!

[Former Member]

Hi,

When I try to run from bin directory its giving 'osql' is not recognised internal or external command

I cant find osql anywhere in the server

SAPup is upto date

Please advise

Thanks,

Santosh

[Former Member]

Hi,

It was there(osql under \binn) in database server. When I ran

osql -E -S AUS-SAPBWDB1 -Q "select VERSION from SVERS" -n

its giving me Invalid Object name "SVERS".

As I said it is named instance BWQ. When I run it in query analyser with setuser 'bwq' its giving me the result "640"

Do I need to change any parameters?

Thanks

Santosh

[Matt_Fraser]

Santosh,

The "setuser 'bwq'" command is setting a default schema for your query analyzer session. Since you don't have this parameter set in osql, to be successful the command would have to include the schema name 'bwq' when reference the table object, i.e.

osql -E -S AUS-SAPBWDB1 -Q "select VERSION from BWQ.bwq.SVERS" -n

Try that at the command prompt/OS level and see if it returns the same result you got in query analyzer.

Regards,

Matt

Edited by: Matt Fraser on Oct 4, 2008 2:39 PM

[Former Member]

Hello Santosh,

Have you updated your SAPup? If no, then please refer note 821032.

Thanks

Dhiraj