9.1D on PA-RISC HP-UX 11iv2 and Client MFGPRO(eB2sp3) on HP rx3600 - NOT CONNECTING

[lenindasan]

Hi,

Our Progress is 9.1D09 for 64 bit of PA-RISC and it's runs on HP 9000 rp7410 - HP-UX 11iv2 as Database server and QAD's MFGPRO- eB2SP3 is application.

Remote Client / PROMON able to connect from HP9000 rp7410 ( -H prodb00), where Progress 9.1D09 is running,But not able to connect from Application server of rx3600-11iv2 ( -H mfgpro01) and get's the following error.

─────────────────────────────── Error ─────────────┐
** There is no server active for database /test-irwp-rp/irwp_pmfg on -H │
prodb00 -S irwp_xtratmfg. (704) │
.................................................................................................................................................

Note: rx3600 -11iv2 is having another instance of 9.1D09 and able access it by MFGPRO-eB2 sp3 from rx3600 itself.

My intention is a dedicated Database server ( Progress 9.1D09) and dedicated application server ( QAD's MFGPRO-eB2sp3) and HP Lefthad P4300 iSCSI storage for DB extents for best resource utilization with high Performance of appliocation.

please help me.

 

[TomBascom]

Re: 9.1D on PA-RISC HP-UX 11iv2 and Client MFGPRO(eB2sp3) on HP rx3600 - NOT CONNECT

9.1d09 is ancient, obsolete and unsupported.

The only "supported" release of version 9 is 9.1e04 -- and that was released 6+ years ago.

Using such an ancient release is not compatible with a desire for "best resource utilization with high performance of application".

Anyhow, the error that you report usually means just what it says. That you have not started a server for database /test-irwp-rp/irwp_pmfg on host prodb00 at port irwp_xtratmfg. Or if you have started such a server it cannot be found with those values (BTW -- you only need the db name if you're using a remote connection -- not the full path).

That could be because of a spelling problem or it could be because the port isn't correctly configured in /etc/services or you might have a messed up conmgr.properties (if you're using that) or it might be firewall rules or a million or so other things. The db log on prodb00 should reveal the -H and -S information that it used if you started a broker to accept connection requests. I'd start debugging by verifying that.