[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::sql_services

Title:SQL/Services Forum
Notice:kits(3) ft info(7) QAR access (8) SPR access (10)
Moderator:SQLSRV::MAVRIS
Created:Thu Oct 13 1988
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2214
Total number of notes:8586

2188.0. "QPT not working with 7.0 server" by ITVMS1::MFERRARI (Murphy was an optimist) Fri Apr 11 1997 09:14

Hi all,

I just installed Rdb7 MV on an Alpha 8400 cluster (VMS 6.2-1H3 with all the
recommended patches), and installed SQL/Services 7.0 as well. I'm experiencing
a strange problem with DBApack. 4 out of the 5 utilities work fine, i.e. I can
connect to a 7.0 Rdb database and work with it, while the Query Performance
Tuner seems to be hooked to the 6.0 server. I tried to explicitly declare the
port # in the sqsapiw.ini file, but to no avail. Is there anything I can do to
force the QPT client to use the 7.0 server?

Thanks in advance,

	/max
T.RTitleUserPersonal
Name		DateLines
2188.1Is the service using Rdb V7.0chsr38.ch.oracle.com::RROHRCajun? Zeydeco? Both!Fri Apr 11 1997 09:515
    The query performance tuner asks for a service name. Is this service
    configured to run Rdb V7.0? You can check this in the SQL Services
    Manager.
    
    /Regina
2188.2ITVMS1::MFERRARIMurphy was an optimistFri Apr 11 1997 09:5722
>    The query performance tuner asks for a service name. Is this service
>    configured to run Rdb V7.0? You can check this in the SQL Services
>    Manager.

Hi Regina, thanks for your answer.

The problem is that I cannot connect to the server containing the services that
I configured. I tried the following:
1. Activate the SQL Services manager on the PC
2. Create a new service called Test under the 7.0 server
3. Activate the SQL services manager on the Alpha and verified that the service
was created correctly.
4. Activate QPT specifying TEST
5. The service is not even recognized

If I ask for the GENERIC service, I'm able to connect to 6.0 databases; as soon
as I try to specify a 7.0 db, it fails saying that the on-disk structure (7.0)
is incompatible with the sw version (6.0).

Cheers,

	/max
2188.3chsr38.ch.oracle.com::RROHRCajun? Zeydeco? Both!Fri Apr 11 1997 10:1513
    Buon giorno Max,
    
    I just created a service TEST and it works ok. When you create it you
    are asked if you want to start it. Is this service started (i.e. does
    not have a red cross)?
    
    Did you try to double click the generic service, change the SQL version
    to 7.0? It will then tell you that you have to restart the server. Do
    that.
    
    /Regina
2188.4ORAREP::ROM01::HITECHBruno CipollaFri Apr 11 1997 13:3730
Hi Regina,

(dont't look at the account, it's still me...)

>    I just created a service TEST and it works ok. When you create it you
>    are asked if you want to start it. Is this service started (i.e. does
>    not have a red cross)?
    
The service is started, and it works fine with (for example) RMUwin, or the
performance monitor. The problem seems to be somehow related to the client that
can't decide on what of the two servers go. I forgot to mention that both 6.0
and 7.0 servers are started, each of them has its own services.

>    Did you try to double click the generic service, change the SQL version
>    to 7.0? It will then tell you that you have to restart the server. Do
>    that.
    
I tried everything of the above, with no success. After maaaaany testing, I came
to the conclusion that the solicited server is the 6.0 one. At this point I
can't say if the problem could be some stupid UCX parameter, or some SQLSRV
server parameter, or what else.... I'm a real bozo in networking, but this seems
really strange! :-))

Cheers,

	/max

>    Buon giorno Max,
    
Forse potremmo continuare in italiano? ;-)
2188.5ITVMS1::MFERRARIMurphy was an optimistFri Apr 11 1997 16:2714
Problem solved!!!

I said I'm a networking bozo, didn't I? Well, I misread the instructions in the
sqsapiw.ini file, in that I missed to understand that I had to create a section
with the name of the host, while I left the [RDBSRV] template in place!

Once I defined the TCP/IP port to 119, *and* the version of the generic service
to 7.0, everything worked like a charm!

Thanks Regina for your help.

Ciao,

	/max