SetupCCR Fails If /TMP Is Located On A Different FileSystem (Doc ID 790486.1)

Last updated on AUGUST 31, 2021

Applies to:

Symptoms

The following is the configuration input and output:

:/PATCH/u01/app/PATCH/product/10.2.0/ccr/bin> setupCCR -s -d 12345678
 <EMAIL>@<HOSTNAME.DOMAIN> CA
 mv:
 /PATCH/u01/app/PATCH/product/10.2.0/ccr/hosts/lpenachobde/config/collector.properties: unable to duplicate owner and mode after move.
 mv:
 /PATCH/u01/app/PATCH/product/10.2.0/ccr/hosts/pb10orafn2dev/config/collector.properties: unable to duplicate owner and mode after move.

Changes

In this case, the Oracle Configuration Manager was downloaded onto a Windows machine and then SFTP over onto an AIX machine for extraction.  The extraction itself and the installation was being performed on different filesystem and therefore the internal coding call of setupCCR was being compromised since a 'MV:' is being conducted which looks for the /TMP directory and it's proper permissions.  These permissions are of course being based on where it was originally extracted.    

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.