On solaris sparc mini cluster the database home installation pre-eq checks were failing with following errors, though these errors are not reported during installer checks.
A00100 OS Type RECORD SunOS SPARC 2.11 64-bit
A00200 OS Certified? PASSED Certified
A00210 Got Maint Updates? FAILED NoMaintUpd
A01010 ApplTierDirectory RECORD /u01
A01020 A_T Valid? PASSED ATexists
A01030 A_T Permissions OK? PASSED CorrectPerms
A01040 A_T Disk Space PASSED Available
A01400 Got Software Tools? PASSED tools_found
A02020 ulimits OK? FAILED NoFilesTooSmall StackTooSmall
A02210 Kernel Params OK? PASSED KernelOK
A03010 Space in tmp PASSED Available
A03510 IP Address RECORD 192.168.200.204
A03530 Domain Name RECORD ijarah.loc
A03540 /etc/hosts Format PASSED Adequate IPv4 entry
A03550 DNS Lookup PASSED Host correctly registered in DNS
A03560 Net Service Access? PASSED NonExist
A03570 Port 6000 PASSED Free
A03620 anon port range OK? FAILED tcp_smallest tcp_largest udp_smallest...
A04400 Got OS Packages? PASSED All required OS packages are installed
A05400 Solaris 10 Patches? SKIPPED Not on Solaris 10 SPARC
Result file: output/collect/APPS_HCVE_A_EBS122_sol_res.htm
root@ijrpserpapp-t1:/u01/rda/rda#
The above checks are using "rda.sh" script , It failed on following rules:
A02020 ulimits OK? FAILED NoFilesTooSmall StackTooSmall
A03620 anon port range OK? FAILED tcp_smallest tcp_largest udp_smallest...
Solution:
we can use following commands to fix this issues:
To fix Rule "A02020 ulimits OK?"
projmod -s -K "process.max-stack-size=(privileged,32MB,deny)" user.oracle
projmod -s -K "process.max-file-descriptor=(privileged,1024,deny)" user.oracle
projmod -U oracle -sK "process.max-file-descriptor=(basic,65536,deny)" user.oracle
projmod -U oracle -sK "project.max-shm-memory=(priv,32G,deny)" user.oracle
To fix Rule "A03620 anon port range OK? "
ipadm set-prop -p smallest_anon_port=9000 tcp
ipadm set-prop -p largest_anon_port=65500 tcp
ipadm set-prop -p smallest_anon_port=9000 udp
ipadm set-prop -p largest_anon_port=65500 udp
All these commands should be exucted as root user and its recommended to use fresh session to avoid this issue being reported again.
thanks for reading :)
regards,
X A H E E R
Comments