If you face this error while creating materialized view:
ORA-30373: Object Data Types Are Not Supported In This Context
This means you are trying to create a Materialized View that references columns data types such as XMLTYPE or SDO_GEOMETRY or ESRI ST_GEOMETRY. This is a 12c limitation.
On the other hand, if you try to crate a materialized view with ST_GEOMETRY column this won’t be allowed.The workaround is not including the ST_GEOMETRY attribute in the materialized view.
This error is received in 11g release, but fixed in 12c release :
ORA-29532: Java call terminated by uncaught Java exception: java.lang.RuntimeException
ORA-06512: at “MDSYS.SDO_UTIL”, line 196
is there any workaround for this problem in 11g …. YES:
1. Drop the spatial index on the geometry table
2. Run the update
3. Rebuild the spatial index
When installing Oracle 12cR2 binaries there are 2 methods:
Here I am going to choose option 1 which using OUI GUI
After installing the zip file from Oracle website, unzip it and run setup.exe file
Then choose “Next”:
Choose “Yes”
Here I am going to choose “Upgrade an existing database” option
I will choose “Enterprise Edition”
To explain these options:
In previous release you didn’t have option number one which is “virtual account” option. The virtual account is a feature that has been introduced since windows releases (Windows 7 & Windows Server 2008 R2).
Option1: Virtual accounts are locally managed accounts that has No password management requirement, and the ability to access, Oracle is recommending to use it so….use it especially for fresh new database creation.
Option2: using existing account which is a managed active directory domain account created by Active Directory Administrators.
Option3: is for creating a new local windows server account and setting the password for it.
Option4: is the built in SYSTEM windows account, which is not preferred option for security reasons.
*** Warning: if you are upgrading an already existing database, then use the service account you have already configured previously. This what i am going to choose in my illustration and practice. Otherwise you will face the below error when using “virtual account” option:
To continue…
choose “install”
specify the service account and password:
Pre-upgrade check will be running
Here I am facing 2 problems that I need to resolve:
SQL> purge dba_recylebin;
After fixing the errors, we can proceed as shown below:
In case of upgrade failure, I have chosen “RMAN” technique for restore, you can use “flash back”if you prefer but you need to make sure you have set flash recovery area in your init.ORA:
Verifying by querying v$version view:
And that’s it …. Good Luck.
This could be known and primitive to many people, however i am putting it to help the community in general from different technical-levels.
when you initiate sqlplus and trying to connect to your database instance you face the following error:
ORA-12560: TNS:protocol adapter error
if you are using windows OS, you need to check the following:
set ORACLE_HOME=D:\app\db33\product\12.1.0\dbhome_33
set ORACLE_SID= ORACLE33
set PATH=D:\app\db33\product\12.1.0\dbhome_33\bin
to check that its reflected, execute the following to verify the value of ORACLE_HOME:
echo %ORACLE_HOME%
now try initiating sqlplus and it will be working 🙂
Geodata Master 