ADRCI IPC PACK INCIDENT command fails with "Can't Locate {file name} In @INC" errors
Last updated on DECEMBER 13, 2017
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
While creating an ADRCI package in a GRID environment there are errors reported such as "Can't locate {file name} in @INC ... ".
These errors are accompanied by compilations errors:
adrci> set home diag/rdbms/sigprod/sigprod_1
adrci> ips pack incident 867483 in /tmp
Can't locate Carp.pm in @INC (@INC contains: /u01/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi /u01/oracle/11.2.0/grid_4/perl/lib/5.10.0 /u01/oracle/11.2.0/grid_4/perl/lib /hostname/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi /hostname/oracle/11.2.0/grid_4/perl/lib/5.10.0 /hostname/oracle/11.2.0/grid_4/perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /hostname/oracle/11.2.0/grid_4/perl/lib/site_perl/5.10.0 /hostname/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi /hostname/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi /hostname/oracle/11.2.0/grid_4/perl/lib/5.10.0 /hostname/oracle/11.2.0/grid_4/perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /hostname/oracle/11.2.0/grid_4/perl/lib/site_perl/5.10.0 /hostname/oracle/11.2.0/grid_4/perl/lib/site_perl .) at /u01/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi/Sys/Hostname.pm line 5.
BEGIN failed--compilation aborted at /u01/oracle/11.2.0/grid_4/perl/lib/5.10.0/x86_64-linux-thread-multi/Sys/Hostname.pm line 5.
Compilation failed in require at /u01/oracle/11.2.0/grid_4/bin/diagcollection.pl line 83.
BEGIN failed--compilation aborted at /u01/oracle/11.2.0/grid_4/bin/diagcollection.pl line 83.
Generated package 2 in file /tmp/ORA600kff_20150204143209_COM_1.zip, mode complete
The issue has already been described by the following note
<Note 1921317.1> - ADRCI IPS Command Fails with Can't Locate Sys/Hostname.pm
While the document addresses an issue with files Hostname.pm and strict.pm there could be further files affected having different extensions and changing the protections for Hostname.pm and strict.pm might not be sufficient to stop the errors.
Changes
This occurs since having upgraded the Grid Environment to 11.2.0.4.
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms