Error
Could not connect 'Ethernet0' to virtual network 'VMnet0'.
More information can be found in the vmware.log file.
Failed to connect virtual device 'Ethernet0'.
3. It will open below wizard and click on change settings .
4. Click on restore default and wait to complete. once reset completed start your machine.
If hostname changed (click here) and ORACLE ASM restart is not able start and connect,
Hello Friends,
When I was working on new machine and install VMware 17 Pro, I copied backed up VM machine to new machine and started VM, It was showing below error.
Error :
Unable to open kernel device '\\.\VMCIDev\VMX': The operation completed successfully. Did you reboot after installing VMware Workstation?
Module 'DevicePowerOn' power on failed.
Failed to start the virtual machine.
====================================================================================================
Solution :
I have copied/restored VM to "D:\VMware\VM2\EL_7.9" .
1. Go to your VM directories.
2. take backup of VMware virtual machine configuration (.vmx), as highlighted.
3. Open OEL7.9 in notepad and search for vmci0.present. If it has set with TRUE value. Make it FALSE. shown as below.
4. Restart your VM machine, it will run without any error.
Feel free to share if issue not fixed.
Hello Friends,
As from oracle 19c, Oracle started to provide database upgrade using autoupgrade features, It also provide report of preupgrade we have in traditional method but here you can get that report in HTML and easy to focus on error.
Important point is DBA must be keep practicing to check flashback status on tablespace too if you are using tablespace during time of any activity.
You may check it with the hep of "select name, flashback_on from v$tablespace "
You face issue related to TBLSPACE_FLASHBACK_OFF is failing during prechecks stage. Error could be same as showing error in red box and description. Please refer solution which fixes the issue.
As the AutoUpgrade utility creates restore points by default, enable flashback for the tablespace(s) that have flashback off prior to upgrading. For more details, refer to the section on "Using Flashback Database and Restore Points" in Oracle documentation "Backup and Recovery User's Guide".
Note: To find tablespaces with flashback off, run: select name from v$tablespace where flashback_on = 'NO';
Flashback is not possible if at least one tablespace in the database has flashback disabled.
At least one tablespace in this database has flashback off. To find such tablespaces, run: select name, flashback_on from v$tablespace where flashback_on = 'NO';
SQL> select name, flashback_on from v$tablespace ;
NAME FLA
------------------------------ ---
SYSTEM YES
SYSAUX YES
UNDOTBS1 YES
TEMP YES
USERS YES
DATA_SCOTT NO
INDX_SCOTT NO
SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 3.2212E+10 bytes
Fixed Size 12178656 bytes
Variable Size 1.6643E+10 bytes
Database Buffers 1.5502E+10 bytes
Redo Buffers 54927360 bytes
Database mounted.
SQL> alter tablespace DATA_SCOTT flashback on;
Tablespace altered.SQL> alter tablespace INDEX_SCOTT flashback on;
Tablespace altered.SQL> select name, flashback_on from v$tablespace ;
NAME FLA
------------------------------ ---
SYSTEM YES
SYSAUX YES
UNDOTBS1 YES
TEMP YES
USERS YES
DATA_SCOTT YES
INDX_SCOTT YES
SQL> alter database open;
Once it started to show All tablespace flashback_on is YES, you may resume upgrade job.
Please share your feedback if this didn't works.
