Video on Client Side Failover in RAC
-
I've posted a new video demonstrating Client Side Failover defined by the
tnsnames.ora file
Acum o săptămână
You've got to have a dream. When you lose your dreams, you die.
The opatch minimum version check for patch /oradata/patches_oracle_software/13696242_GI_DB/13696242/custom/server/13696242 failed for /product/11gR2/db_1 The opatch minimum version check for patch /oradata/patches_oracle_software/13696242_GI_DB/13696224 failed for /product/11gR2/db_1 Opatch version check failed for oracle home /product/11gR2/db_1 Opatch version check failed update the opatch version for the failed homes and retry
Cause : upgrade also the OPatch from the Oracle database software .
See also the oracle metalink below for other possible causes
mkdir /ramfs
mount -t ramfs -o size=500m ramfs /ramfs
In your oracle database ( as user sys or system ) :create temporary tablespace temp_ramfs tempfile '/ramfs/temp_ramfs.dbf' size 10M autoextend on next 10M maxsize 32G; alter database default temporary tablespace temp_volatil ;
While editing a file, Microsoft office 2007 writes the content to a temporary
file and renames the temporary file to the original file name while saving.
When this happens the file's create time stamp will reflect the create
time stamp of the temproary file which would be different from the original
create time of the file. So after this happens, windows client will have to
send a CIFS request to restore the create time stamp to the original value.
However, this request will be sent only when the share permission is set to
full control. In all other cases the create time will have the modified time.
Solutions :
1. Change the share permission to full control.or 2. Upgrade to Office 2010.
Another workaround
https://kb.netapp.com/support/index?page=content&id=3011249 Increase CIFS Max Multiplex