Oracle CPU Kills Esri
Just applied the October 2014 Oracle Critical Patch Update (CPU) to some Esri geodatabases and the results were not good.
After applying patch 19618575 patch 34 to several ArcGIS 10.0 geodatabases (22.214.171.124) all Esri products ceased to function properly. You may receive an error message stating “ArcMap has encountered a problem and needs to close.” In addition, ArcGIS for Server map services will stop and return the error “Unable to Start service Server Object instance… creation failed on machine” if you attempt to start them.
The only way we found to fix this issue is to perform a rollback of the patch, taking the databases back to their default state, then apply the Oracle CPU released in July 2014. The instructions for performing the rollback can be found in the patch’s readme file.
UPDATE #1: It took them over a week to respond, but Esri has finally acknowledged there is a problem with the latest Oracle patch. The details can be found in Knowledge Base Article ID 43293.
Update #2: Instead of granting the select privilege on v_$parameter to each database user we created a new default role, granted the select privilege on v_$parameter to the role, and assigned the default role to each user via Oracle Enterprise Manager. This provides admins with a quick method for adding other privileges in the future.
Comments are closed.