V6.1 - Unable to connect to database error

Yahoo Archive
1
I had this when we moved to our new server. I ended up setting the mfgsys.pf -mm setting to 1024 and using PET on the server to change that side (Message Buffer Size) to 1024 as well. Required DB stop/restart. I was under the gun to make it work quickly so never went back to trying 4096. My understanding was 4096 was more effecient spacewise but 1024 better for speed. Or something like that. Once reports would run I stopped worrying about it.
-Todd C.

________________________________
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Ted Kitch
Sent: Tuesday, July 01, 2008 1:58 PM
To: vantage@yahoogroups.com
Subject: [Vantage] v6.1 - Unable to connect to database error


I've recently setup a virtual machine instance of our Vantage server for
testing and after copying the installation to the new drive and correcting
all of the drive letters & path statements in the various files, I have one
that I've been unable to correct.

The error message that I get is when I try to run any of our report builder
reports. Here is the message:

Unable to connect to database. Database error is: Server has -Mm parm 4096
and client has 1024. They must match. (1150).

I've modified the .pf file to show 4096, but I still get the error.

Any ideas?

Ted Kitch

Information Technology Manager

Astro Machine Corporation

www.astromachine.com

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
2
I've recently setup a virtual machine instance of our Vantage server for
testing and after copying the installation to the new drive and correcting
all of the drive letters & path statements in the various files, I have one
that I've been unable to correct.



The error message that I get is when I try to run any of our report builder
reports. Here is the message:



Unable to connect to database. Database error is: Server has -Mm parm 4096
and client has 1024. They must match. (1150).



I've modified the .pf file to show 4096, but I still get the error.



Any ideas?



Ted Kitch

Information Technology Manager

Astro Machine Corporation

www.astromachine.com





[Non-text portions of this message have been removed]
3
Is the computer on which you are running the VM listening on 4096 perhaps? I had all kinds of problems with ports on VMs, now I have pretty much stopped using any products on VMs that require port management or mapping.

Is the NIC for the VM bridged?

Thanks,
Kunal



----- Original Message ----
From: Ted Kitch <tkitch@...>
To: vantage@yahoogroups.com
Sent: Tuesday, July 1, 2008 1:58:28 PM
Subject: [Vantage] v6.1 - Unable to connect to database error


I've recently setup a virtual machine instance of our Vantage server for
testing and after copying the installation to the new drive and correcting
all of the drive letters & path statements in the various files, I have one
that I've been unable to correct.

The error message that I get is when I try to run any of our report builder
reports. Here is the message:

Unable to connect to database. Database error is: Server has -Mm parm 4096
and client has 1024. They must match. (1150).

I've modified the .pf file to show 4096, but I still get the error.

Any ideas?

Ted Kitch

Information Technology Manager

Astro Machine Corporation

www.astromachine. com

[Non-text portions of this message have been removed]






[Non-text portions of this message have been removed]