Please see as well:
Yesterday and the day before I’ve exchanged several emails with Ana who downloaded our Hands-On-Lab from here:
after OOW15, encountering a SEGMENTATION FAULT when trying to start the database upgrade with catctl.pl:
$ $ORACLE_HOME/perl/bin/perl catctl.pl catupgrd.sql
Very strange thing …
The database is in upgrade mode (checked this in the alert.log) and there are no strange things mentioned anywhere. Plus hundreds of people have run and completed our lab so far.
Tue Nov 10 20:39:47 2015 MMON started with pid=21, OS id=9828 Starting background process MMNL Tue Nov 10 20:39:47 2015 MMNL started with pid=22, OS id=9832 Stopping Emon pool Tue Nov 10 20:39:47 2015 ALTER SYSTEM enable restricted session; Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET _system_trig_enabled=FALSE SCOPE=MEMORY; Autotune of undo retention is turned off. Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET _undo_autotune=FALSE SCOPE=MEMORY; Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET undo_retention=900 SCOPE=MEMORY; Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET aq_tm_processes=0 SCOPE=MEMORY; Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET enable_ddl_logging=FALSE SCOPE=MEMORY; Resource Manager disabled during database migration: plan '' not set Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET resource_manager_plan= SCOPE=MEMORY; Tue Nov 10 20:39:47 2015 ALTER SYSTEM SET recyclebin='OFF' DEFERRED SCOPE=MEMORY; Resource Manager disabled during database migration replication_dependency_tracking turned off (no async multimaster replication found) AQ Processes can not start in restrict mode Starting background process CJQ0 Tue Nov 10 20:39:47 2015 CJQ0 started with pid=27, OS id=9836 Completed: ALTER DATABASE OPEN MIGRATE
We checked several other things – and then I came across this tweet by Martin Klier yesterday:
I have no 100% proof for the actual reason but several people seem to have issues with SEGMENTATION FAULTs in Oracle’s PERL ($ORACLE_HOME/perl/bin/perl) when using Oracle VirtualBox 5.0.x – and according to VitualBox Forum that seems to happen with the most recent VBox 5.0.10 as well.
The “funny” thing is that all works perfectly well in VBox 4.3.x …
It reminds me a lot on the reoccuring VBox bug with my German keyboard not allowing me to type in the | (pipe) character which requires to press “ALT GR” + “<” keys together.
I have described this issue in this blog post http://laurent-leturgez.com/2015/05/26/oracle-12c-vmware-fusion-and-the-perl-binarys-segmentation-fault
You will find some workarounds in.
Laurent Leturgez had published his workaround for same issue on VMWare: http://laurent-leturgez.com/2015/05/26/oracle-12c-vmware-fusion-and-the-perl-binarys-segmentation-fault/
I’m running Version 5.0.8 r103449 of Virtual Box on OS X. While working on following lab.
I get "segmentation fault". I’m not sure if this is the same bug that you’re hitting.
Thanks for all your comments and the workaround hints.
What really bugs me here:
I didn’t create a new VBox image. Ours is several months old and got used by thousands of people.
Why the heck is a new version of VBox (5.x) causing PERL to segfault?
In my case, I didn’t have the problem on VBox running on Windows but only on my mac.
One of the guy who commented my blogpost, said he workarounded the problem by changing the paravirtualization interface.
So, It might be related to the hypervisor only in mac.
If you are using a standalone server and you don’t use containers, or oracle perl scripts (catctl.pl etc.) … the problem will never occur. (I remembered I asked to people and they never faced the problem because of that).