I,m installing Oracle Apex on Oracle database 11g I did the following steps:
Created tablespace:
CREATE TABLESPACE apex DATAFILE 'D:\oracle\app\ali\oradata\orcl2\APEX5.DBF' SIZE 100M AUTOEXTEND ON NEXT 1M;
sqlplus sys as sysdba.
#apexins.sql APEX APEX TEMP /i/;
Then stared installing but it stopped with the following error :
...Internal messages
begin
*
ERROR at line 1:
ORA-04063: package body "APEX_050100.WWV_FLOW_LANG" has errors
ORA-06508: PL/SQL: could not find program unit being called:
"APEX_050100.WWV_FLOW_LANG"
ORA-06512: at "APEX_050100.WWV_FLOW_API", line 2149
ORA-06512: at "APEX_050100.WWV_FLOW_API", line 26722
ORA-06512: at line 2
Any help is appriciated ..thank you.
Which versions (both Apex and Oracle database) do you use, exactly?
APEX_050100 suggests that it is Apex 5.1. If that's so, note that minimum Oracle database version you can use with it is 11.2.0.4.
Therefore, you might need to upgrade database version or - if you can't do it - install lower Apex version (note #2 that Apex 5.0.x requires at least 11.1.0.7).
I believe your problem is that Apex 5 must be installed in ASSM tablespace. You need to uninstall Apex, and create a new APEX5 tablespace with ASSM. See this page for more help: Apex-Help-Article.
The gentleman is right.
Apex 5.1 DB Requirements
Above Apex version 20.2.0.00.20, you must user 12c or higher.
I suffered from it some time ago
Issue due to using non-certified version of database.
Attempting to install APEX 5.1 on a 11.1.0.7 Oracle Database which is not compatible/certified with this version of APEX.
Beginning with Application Express 5.1, the minimum database version requirement is 11.2.0.4.
For more information regarding the minimum requirements for APEX 5.1, review the documentation:
https://docs.oracle.com/database/apex-5.1/HTMIG/Oracle-AE-installation-requirements.htm#HTMIG376
2.1 Oracle Database Requirements
'''''''''''''''''''''''''''''''''''''''''
Oracle Application Express release 5.1 requires an Oracle Database release 11.2.0.4 or later, including Enterprise Edition and Express Edition (Oracle Database XE)
Soluation for this problem
Install 5.0.x APEX which is certified with minimum 11.1.0.7 version of Database (http://www.oracle.com/technetwork/developer-tools/apex/downloads/apex-5-archive-2606313.html)
OR
Upgrade your Database to version 11.2.0.4 or later and then install the latest version of APEX (5.1.x)
Related
Does flyway community version support Oracle 19c? From this URL: https://flywaydb.org/documentation/database/oracle, it is up to 19.3. My oracle database is 19.7. I am not very familiar with oracle database versions.
Any version support oracle 19.7 at all?
Thanks!
Assuming no breaking changes have appeared in Oracle 19.7, then yes, we just have not formally tested it yet. If you try, you will get a warning to this effect in the log but Flyway will function as normal. I'll update the tests and remove this warning for the next patch version.
I am trying to utilize the RODBC::sqlSAVE() function in R, but I am getting an error that HY000 -9719 [Teradata][ODBC Teradata Driver][Teradata Database] QVCI feature is disabled. which is throwing an error. How can I enable QVCI in Teradata? I am using ODBC to connect, version 16.20 on Windows via ODBC Administrator.
Must be a very early version of Teradata 16.20 client driver. Upgrade to current patch level of Teradata ODBC, or consider switching to Teradata SQL Driver for R.
I cannot get VS 2015 to create my EDMX file for an Oracle Connection.
I am using Visual Studio 2015 Update 3
I have installed the Oracle Developer Tools 12.1.0.2.4
I have installed Oracle Data Access and the following DLLs exist under \ client[user]\product\12.1.0\client\odp.net\bin
2.x\Oracle.DataAccess.dll version: 2.121.2.0 ODAC Release 4
4\Oracle.DataAccess.dll version: 4.121.2.0 ODAC Release 4
I am using the following assemblies
Oracle.ManagedDataAccess Version: 4.122.1.0
Oracle.ManagedDataAccess.EntityFramework Version: 6.122.1.0
* I believe both of these are version 12.2.1100 based on the folders in which they reside in the packages folder.
There are no connections defined in the Server Explorer
My steps are as follows:
Within the Solutions Explorer, Right click on project and select "Add" | "New Item..."
Select Data | ADO.NET Entity Data Model | Add
Select EF Designer from Database | Press Next
In the Entity Data Model Wizard:
Press New Connection... (I get an warning "Failed to find the default tnsnames.ora file." I ignore and press "OK"
With the Datasource as "Oracle Database (ODP.NET, Managed Driver)" I enter the credentials and specify the the other
connection parameters and press "Test Connection" which SUCCEEDS.
I press OK and am taken to the next page in the Entity Data Model Wizard
I include sensitive data in connection string and Press Next....
WIZARD SHUTS DOWN (crashes) - NO EDMX CREATED
Any assistance in helping me troubleshoot this would be greatly appreciated.
TIA - Xavier
Thanks to #Hong-vit pointing me in the right direction. I found the answer.
When you visit the download page for ODAC you're given a selection of version numbers.
In my case the top two were:
ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.0)
ODAC 12c Release 4 and Oracle Developer Tools for Visual Studio (12.1.0.2.4)
For me the top one wouldn't install. It would cut out during the installation process (thanks Oracle!) so I settled with the second one (12.1.0.2.4).
This meant that when I installed Oracle.ManagedDataAccess and Oracle.ManagedDataAccess.EntityFramework I had to select the correct version.
Not for me:
The one I needed
As you can see the version numbers (almost!) match up:
ODAC 12.2.0.1.0 = Oracle.ManagedDataAccess 12.2.1100
ODAC 12.1.0.2.4 = Oracle.ManagedDataAccess 12.1.24160719 (yay!)
I believe this is a failing on oracles behalf as it's not made clear despite their inclusion on a page long readme on which this doesn't feature. In additon the version numbers not quite being the same...but that's a rant for the blog.
I have the same bug. I fixed it successfully by follow this step:
On your project Right click -> Select Manage NuGet packages on Browse tab input oracle. You will see Oracle.ManagedDataAccess.EntityFramework. Select version of oracle you have installed. This should be 12.1.2400. Install it, you are done
I had the same issue - I hope I can help fellow Googlers having the unfortunate task of connecting Oracle and Visual Studio.
I followed the steps and still got crashes - because I was using VS2017 (I understand that the questions is tagged VS2015). You'll need to install the VS2017 ODAC Client. Thankfully, this one actually does something when you begin the installation. The installer in the link on the accepted answer will only work for VS2015.
The most recent version (as of this time of writing) of ODP.NET is 18.3, which can be installed through NuGet (Oracle.ManagedDataAccess.EntityFramework). Follow these steps on Oracle's website and you'll be setup.
...Or so you think. I got the same error as in this stack overflow question, where it won't go past the Entity Data Model Wizard.
I applied every configuration in the selected answer, but it still wouldn't work. When I downgraded my Oracle.ManagedDataAccess.EntityFramework from 18.3.0 to 12.2.1100, I could finally create my models!
I have had the same problem when I was trying to connect Oracle Entity Framework with Visual Studio 2017.
After install and unistall several times differents version. The build that better works for me is:
Oracle Developer Tools for Visual Studio 2017 (ODTv2017) v12.2.1200
Oracle.ManagedDataAccess v12.2.1100
Oracle.ManagedDataAccess.EntityFramework v12.2.20190115
EntityFramework .NET v6.3.0
I think that having similar versions in Oracle packages is very important for good performance.
It looks like someone here had similar issue: He add to change implementation somehow.
[in this ]case a View (valid and worked) caused the crashes. After changing the implementation without using that view it worked (more or less).
What I advise is you proceed step by step, only importing one object for the first time you test the wizard, then only simple table, then add procedures, views...
I created an MLOAD job using OleLoad on my Windows 7 x64 Professional machine. It loads data from Oracle 11g into Teradata 14. Everything works great when I run it locally. When I copy it to a remote Windows Server 2003 SP2 machine and run it, it fails with error code 12 and this message:
**** 07:30:57 UTY4203 Attempted to access out of range input data in field
'LOCATION_CODE', file 'myjob.amj',record number '1'.
**** 07:30:57 UTY4023 Access module warning '33' received during
'PreserveRestartInfo' operation: 'Attribute name not recognized by attached
AM'
I opened my .amj file on the remote machine to see what it would look like if I regenerated it using OleLoad's UI. When comparing the two .amj files in Beyond Compare afterward, I was surprised to see that the new .amj is very different. VARCHAR(214) is changed to FLOAT, VARCHAR(30) is changed to VARCHAR(10), etc.
All TTU 14 assemblies on the remote machine match what I have installed locally. The only difference I noticed is the verison of Oracle DLL that OleLoad appears to be using. Here's what OleLoad says on my machine when I click on Connection Info for my Oracle connection:
Provider
Name: OraOLEDB11.dll
Version: 11.2.0.1.0
DBMS
Name: Oracle
Version: 11.2.0.3.0
And on the Windows Server 2003 machine:
Provider
Name: OraOLEDB.dll
Version: 9.0.1.0.1
DBMS
Name: Oracle
Version: 11g
Now before anyone facepalms with "Well, DUH! There's your problem!", I'll add that it will cause me a great deal of grief if I had to install a new version of Oracle on my local machine because I have a ton of MLOAD files that I've created for personal utilities (helper loads, if you will, for when the business needs ad hoc report). I can't upgrade what's on the remote server because I'd run the risk of breaking all of the other MLOAD jobs that are running there.
I just wanted to mention all of that in case it was relevant, but I am hoping that it's not actually the problem and that there's a way I can get my current file to work without having to uninstall/reinstall/upgrade anything.
I believe that the theory proposed at the end of my OP has been confirmed. I was able to find a machine that had Oracle client 11 installed and migrated my jobs there. They worked flawlessly, so it is most certainly an issue with Oracle 9 client vs 11.
I recently dug up a very old SQL Anywhere database. I have it installed and it kind of works, its only the distributed side of the data, so everything's running via dbeng50 and ODBC.
I would like to migrate this data to MySQL. Is there a way to do this? I attempted to view the data using an ODBC tool but I kept getting error messages saying the ODBC driver doesn't support the version of ODBC behavior.
I guess the database is too old (it's from 1997) - that put's at it SQL Anywhere version 5.
Its also difficult to find the old SQL tools that would help me access these.
Is it possible to use the .db file with a newer version?
Any help or guidance at all would be appreciated.