]]>Lessons learned - Oracle GI and Database Installation on SUSE 12http://m.tkk7.com/wueddie/archive/2016/07/28/431361.htmlInPracticeInPracticeThu, 28 Jul 2016 08:55:00 GMThttp://m.tkk7.com/wueddie/archive/2016/07/28/431361.htmlhttp://m.tkk7.com/wueddie/comments/431361.htmlhttp://m.tkk7.com/wueddie/archive/2016/07/28/431361.html#Feedback0http://m.tkk7.com/wueddie/comments/commentRss/431361.htmlhttp://m.tkk7.com/wueddie/services/trackbacks/431361.html
asm listdisks
--DATA
ls /dev/oracleasm/disks
Installation tasks:
Issue 3: always failed due to user equivalence check after starting installer OUI with user oracle.
however if I manully check with runcluvfy, no issue found at all.
./runcluvfy.sh stage -pre crsinst -n , -verbose
I worked around it by using another user to replace user oracle. but it triggered next issue.
Issue 4: cannot see ASM disks in OUI. no matter how I change the disk dicovery path. the disk list is empty.
but I can find disk manully.
/usr/sbin/oracleasm-discover 'ORCL:*'
Discovered disk: ORCL:DATA
Root cause is that the ASM is configured and created with user oracle. and I aming installing GI
with different user other than oracle; so I cannot see the Disk created.
change owner of disk device file solved the issue.
ls /dev/oracleasm/disks
chown /dev/oracleasm/disks -R
Issue 5: root.sh execution failed.
Failed to create keys in the OLR, rc = 127, Message:
clscfg.bin: error while loading shared libraries: libcap.so.1:
cannot open shared object file: No such file or directory
fixed the issue with command below:
zypper in libcap1
ohasd failed to start
Failed to start the Clusterware. Last 20 lines of the alert log follow:
2016-07-24 23:10:28.502:
[client(1119)]CRS-2101:The OLR was formatted using version 3.
I found a good document from SUSE,
Oracle RAC 11.2.0.4.0 on SUSE Linux Enterprise Server 12 - x86_64,
it make it clear that SUSE 12 is supported by Oracle GI 11.2.0.4, it also mentioned
Patch 18370031.
"During the Oracle Grid Infrastructure installation,
you must apply patch 18370031 before configuring the software that is installed. "
The patch 18370031 is actually mentioned in "Oracle quick installation guide on Linux",
but not mentioned in "Oracle quick installation guide on Linux". I majored followed up
with later one and missed Patch 18370031.
issue disappeared after I installed the patch 18370031.
./OPatch/opatch napply -oh -local /18370031
Errors in file :
ORA-27091: unable to queue I/O
ORA-15081: failed to submit an I/O operation to a disk
ORA-06512: at line 4
solved by change owner of disk DATA related file
ls -l /dev/oracleasm/iid
chown on folder /dev/oracleasm/iid and some .* hidden file.
Issue during DB installation
Issue 6: report error: in invoking target 'agent nmhs'
vi $ORACLE_HOME/sysman/lib/ins_emagent.mk
Search for the line
$(MK_EMAGENT_NMECTL)
Change it to:
$(MK_EMAGENT_NMECTL) -lnnz11
refer to
https://community.oracle.com/thread/1093616?tstart=0
]]>Notes on Gentoo Installationhttp://m.tkk7.com/wueddie/archive/2010/06/03/322633.htmlInPracticeInPracticeThu, 03 Jun 2010 08:33:00 GMThttp://m.tkk7.com/wueddie/archive/2010/06/03/322633.htmlhttp://m.tkk7.com/wueddie/comments/322633.htmlhttp://m.tkk7.com/wueddie/archive/2010/06/03/322633.html#Feedback0http://m.tkk7.com/wueddie/comments/commentRss/322633.htmlhttp://m.tkk7.com/wueddie/services/trackbacks/322633.html
0. failed to emerge gpm when I install the links package.
If I recall correctly, it is resolved by install gpm manually
1. I encounter issue when I install glib 2.22.5.
no update-desktop-database.
which is in dev-util/desktop-file-utils. When I try to emerge it, there is a circular dependency on glib. no solution
and I forget How I resolve the problem.
2. later after I install glib, with ~amd64 keyword I can install gpm-1.20.6, but it conflicts with the manually inatalled gpm.
I remove the conflicted file and emerge successfully.
3. Failed to emerge tiff.
edit packages.keywords to add the following.
/ ~amd64
I am able to use latest tiff in beta-version, which is unstable and masked out.
4. later atk-1.28.0 failed to emerge.
edit /etc/make.conf with the following.
FEATURES="-stricter".
then emerge successfully with only some complain. with out this seting. the warining from GCC will cause that emerge fail.
5. when I run
emerge --update system
actually gcc will be upgraded from 4.3.4 to 4.4.3. but it failed because of compilation warning, again. add "-stricter" into Features variable in /etc/make.conf work around it.
6. The installation takes a long time, the KDE itself take more than 10 hours. There is still a lot of improvement space! Anyway, it is nice to be able to use it daily.