Fixed permission issue with oradata

A recent change has introduced volumes to docker-oracle-xe-11g that broke the initialization of the oracle instance.

This is due to a defect with the recursive copy of the original oradata: cp -r does not retain the original attributes of the files such as owner and group. When oracle initializes, it doesn't have permission to access the oradata. Instead of cp -r, cp -a does the same as cp -r but preserves the attributes. This effectively retains the permission settings of the original oradata.

Author: wleroux

.gitattributes

@@ -0,0 +1 @@
+*.sh eol=lf

assets/startup.sh

@@ -3,7 +3,7 @@
 # Initialize the host's data volume, leaving a trace when finished.
 if [ ! -e /u01/app/oracle/oradata/dataloaded ]
 then
-  cp -r /u01/app/oracle/oradata.orig/* /u01/app/oracle/oradata/
+  cp -a /u01/app/oracle/oradata.orig/* /u01/app/oracle/oradata/
   touch /u01/app/oracle/oradata/dataloaded
   echo "Host data volume was initialized."
 else