Ruan Linehan
2018-09-22 23:59:05 UTC
Hi all,
Earlier today, we were patching a 12C ODA appliance and ran into a
complaint surrounding a requirement to relink the Grid software from UDP to
use RDS instead for the Infiniband before being able to progress further.
So we attempted to follow the ODA documentation instruction to do this, but
ran into some pretty immediate issues.
The problem we faced appeared to surround our steps for relinking the home
binaries (Which subsequently saw +ASM crash).
The error/symptoms we observed appeared to match the below titled MOS
document, and inferred that our relinking was incomplete.
"SKGXP IPC libraries must be the same version [local:RDS,remote:UDP] on
Exadata"
My question though is around the linux make command. This instruction
appeared to be required as part of the steps for relinking once we've
stopped all resources and unlocked the Grid Infra home. I understand that
make is used to do the recompile from source file, and enable, or specify
the option for 'ipc_rds' as per below.
*$ cd $GRID_HOME/rdbms/lib *
*$ make -f ins_rdbms.mk <http://ins_rdbms.mk> ipc_rds ioracle*
But......The ODA documentation we referenced (Apologies but I don't have
the direct link as not posting this from work) did not include the make
command targets clause of "ioracle" however.
So my question(s)...
Can anyone outline the implications of the inclusion of the lib file
"ioracle" clause here as part of the command please?
Will the compile from source, react drastically differently, or not touch
upon all linked library files if the ioracle clause is omitted?
Does the ioracle stipulation restrict the recompilation to a subset or
specific file group?
What we are really looking to determine here is whether we have the correct
command in the ODA documentation for this step.
When we omit the "ioracle" clause, the make command seems to specify, one
solitary lib output file which it first removes and then copies into place.
When we include the "ioracle" clause, as is shown across many many
documentation examples on MOS, it appears to do additional linking steps
and permissions setting which is shown on stdout.
Any and all help is greatly appreciated.
Ruan
Earlier today, we were patching a 12C ODA appliance and ran into a
complaint surrounding a requirement to relink the Grid software from UDP to
use RDS instead for the Infiniband before being able to progress further.
So we attempted to follow the ODA documentation instruction to do this, but
ran into some pretty immediate issues.
The problem we faced appeared to surround our steps for relinking the home
binaries (Which subsequently saw +ASM crash).
The error/symptoms we observed appeared to match the below titled MOS
document, and inferred that our relinking was incomplete.
"SKGXP IPC libraries must be the same version [local:RDS,remote:UDP] on
Exadata"
My question though is around the linux make command. This instruction
appeared to be required as part of the steps for relinking once we've
stopped all resources and unlocked the Grid Infra home. I understand that
make is used to do the recompile from source file, and enable, or specify
the option for 'ipc_rds' as per below.
*$ cd $GRID_HOME/rdbms/lib *
*$ make -f ins_rdbms.mk <http://ins_rdbms.mk> ipc_rds ioracle*
But......The ODA documentation we referenced (Apologies but I don't have
the direct link as not posting this from work) did not include the make
command targets clause of "ioracle" however.
So my question(s)...
Can anyone outline the implications of the inclusion of the lib file
"ioracle" clause here as part of the command please?
Will the compile from source, react drastically differently, or not touch
upon all linked library files if the ioracle clause is omitted?
Does the ioracle stipulation restrict the recompilation to a subset or
specific file group?
What we are really looking to determine here is whether we have the correct
command in the ODA documentation for this step.
When we omit the "ioracle" clause, the make command seems to specify, one
solitary lib output file which it first removes and then copies into place.
When we include the "ioracle" clause, as is shown across many many
documentation examples on MOS, it appears to do additional linking steps
and permissions setting which is shown on stdout.
Any and all help is greatly appreciated.
Ruan