I had to edit the rpc file first but then I did not install ARS as root. I don't know off-hand what version of CentOS I have as the machine is not started.
The install went smoothly. Remember the limits settings as documented by BMC. Follow all the doc steps completely. I also gave the machine two Ethernet cards as Oracle tends to like a fixed IP. (One uses DHCP and the other is hard coded). I always have access to the machine even if I am not on my own LAN that way. Perf is OK. I give the CentOS 8Gb and 2 dual cores on a 16GB and a i7xxx. If I do intensive things (like build 100 archive forms) ARS chews up memory and then I will restart the OS. I find the CentOS perf is better than the Windows Server 2003 x64 / SQL perf but no real performance testing was done. The stack installer completed in under two hours. Cheers Ben From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Nathan Brandt Sent: April-02-13 06:14 To: arslist@ARSLIST.ORG Subject: Re: CentOS 6.3 Installation Port Mapper Issue ** Hi Ben, Overall performance of CentOS 6.3 was also not good. I tried installing it on RHEL 5.3 and all went pretty smooth and I do see all these entries in /etc/rpc # Action Request System daemons arserverd 390600 arserverd arserverd 390601 arserverd arserverd 390604 arserverd arserverd 390619 arserverd arserverd 390620 arserverd arserverd 390621 arserverd ... arserverd 390692 arserverd arserverd 390693 arserverd arserverd 390694 arserverd arserverd 390695 arserverd I am planning to try it on CentOS 6.4. In case, I again face port mapper issues, do I have to manually put these entries in /etc/rpc before starting with the installation? ~ Nathan On Tue, Apr 2, 2013 at 1:03 AM, Ben Chernys <ben.cher...@softwaretoolhouse.com> wrote: ** You need to follow the installation instructions - exactly. I got caught by this too. Change the limits as specified, but your real cause of error is not modifying the rpc file by appending . #Action Request System daemons arserverd 390600 arserverd arserverd 390601 arserverd arserverd 390604 arserverd arserverd 390619 arserverd arserverd 390620 arserverd arserverd 390621 arserverd . . . arserverd 390694 arserverd arserverd 390695 arserverd ################## Cheers Ben Chernys Senior Software Architect Canada / Deutschland Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: Ben.Chernys_AT_softwaretoolhouse.com Web: <http://www.softwaretoolhouse.com/> www.softwaretoolhouse.com We are a BMC Technology Alliance Partner Check out Software Tool House's free Diary Editor and out Freebies Section for a ITSM 7.6.04 and 8.0.0 Fields spreadsheet. Meta-Update, our premium ARS Data tool, lets you automate your imports, migrations, in no time at all, without programming, without staging forms, without merge workflow. <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com/ From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of munesh konda Sent: April-01-13 08:03 To: arslist@ARSLIST.ORG Subject: Re: CentOS 6.3 Installation Port Mapper Issue ** Nathan, Did you check the portmapper process/daemon is running on that box. Also I am not sure whether BMC would support Remedy on CentOS as it is not mentioned in their Comp Matrix. But the Remedy would work on CentOS as it using the bin/lib of RHEL... Thanks. Regards Munesh On Mon, Apr 1, 2013 at 11:26 AM, Nathan Brandt <nathanrbra...@gmail.com> wrote: ** I am trying to install ARS 7.6.04 SP2 on 64 bit Centos 6.3 on top of Oracle database. For now, I am using same machine to install db, midtier and AR Server. This is what I did - Created a user in OS oracle and installed oracle database using this user at /home/oracle/app/ - Installed ARS using root user Installation goes fine, but in the end, during system validation checks, I get a message "AR System Server unable to create (390600, 0) for TCP" User Tool gives this error when trying to connect to AR Server. ARERR [90] Cannot establish a network connection to the AR System server RPC: Program not registered Then I did re-installation with following Register with Portmapper: NO AR System Server TCP Port Number: 8081 AR System Server Plug-in TCP Port Number: 8082 and it worked fine. Are there any issues if we we keep "Register with Portmapper: YES"? ~ Nathan _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
smime.p7s
Description: S/MIME cryptographic signature
