I want to connect my oracle database 21c xe with Oracle Developer 10g (forms/reports)?
I can't find any reference on the Internet (My Oracle Support included). The closest information I managed to find is about Forms 10g on database 19c.
Michael Ferrante (from Oracle) said:
Forms 10.1.2 has been out of support for over 10 years, long before Database 19 was even a "thing". This is not a supported configuration that I would consider for any production environment. That said, some people have claimed to get things working. So, it may be technically possible, although I personally would not do it nor would I recommend it.
If you choose to ignore my warning and recommendation, I will say that if you plan to do it ensure that you are at least running the latest patched version of Forms 10.1 (10.1.2.3 - patch ID 5983622) and have installed the latest/last DB 10.1.0.5 client patch (4505133) into this home. As always, create a backup of the home before attempting to apply any patches.
Following this guidance should help to reduce the risk of having problems.
Therefore, as 21c (XE) is even newer than 19c, you might - or might not - make it work. There's no guarantee that it will.
Related
I need a tool that I can create a phisical schema for my relational database. Something that I create tables, columns and relationships, and the tool generates sql to me.
PowerDesigner example
I've used PowerDesigner for many years in Windows and it has worked good to me. Now I need some similar to use in Arch Linux with gnome. Any suggestion?
oh.. my database is PostgreSQL and I look for something free.
[EDIT] I have tested some alternatives and no one serves me well. SQL Power Architect is discontinued and don't work properly. DBVisualizer is limited in free version. DataModeler don't generate sql how I expect.
I can recommend DbVisualizer. If you are limited by the free version you can start a free trial of the Pro version. On their Postgres page they seem to have what you need. DbVisualizer - PostgreSQL Client
Our main project has been using a now-very-old Flyway version since inception. (v3.2.1)
Flyway has made loads of improvements over the years, and v6+ appears to contain many interesting features for our MySQL schema.
Attempting the supported upgrade path, I ran into a few problems--e.g. our .sql migrations refuse to migrate from start to finish; Flyway v3.2.1 considers all our SQL migration valid, but v4+ chokes on some odd comment syntax. Naturally, file fixups to get migrate working will produce different check sums, which is an obstacle to safe upgrade. I'm well aware of the schema table name change in v5; that's not insurmountable.
I'm also eyeing Liquibase vs. and online schema migration tools; FB, Percona and GitHub's OST (gh-ost) look interesting, but we use foreign keys, and we'd need more replicas, so that may not be in the cards for us right now.
For now, I'm interested in a new baseline w/ Flyway v7 beta or switching tools. If you deploy SaaS on k8s and have any generic advice--I'll take it, but I'm specifically interested in one thing:
How have folks overcome the issue where newer versions of Flyway no longer accept existing SQL migrations. Or, has anyone "given up" and just created a new baseline, rather than doing the long upgrade path? (or, switched from Flyway to another tool with similar merits)
There are at least two problems here, with many moving parts:
Dealing with the tooling's constraints, and how to deal with Flyway 3->7+ (follow the tool's doc)
How to incorporate large prod SQL migrations in general, which is too general a problem to cover here.
If anyone has better (less general) advice on the first, I'd love to hear it.
Re: the second, we're looking to our infra and deployment from off-the-shelf tools.
Most projects I've worked on have been Spring based. (large ecosystem, even without the k8s bits)
You may give a shot to bytebase (bytebase.com).
Web-Based
Open-Source
Can do MySQL schema migration triggered by GitHub/GitLab with full history
Just wondering whether anyone has any views on whether DevArt MySQL is > MySQL Connector ? In the past, when I have used MySQL - the MySQL Connector really sucked for C# ASP.NET development work.
Can anyone please provide an opinion on whether its better to use DevArt or ?
I've just started using the DevArt MySQL connector and it seem to be good so far. One issue that I've discovered, though, is that it doesn't seem to offer the equivalent of a MySqlDateTime type. This means timestamps must map to the DateTime .NET type and the consequence is that a 'zero' timestamp cannot be represented as such and is converted to 01-01-0001 on the .NET side.
Something else you should be aware of is that the (non-DevArt) MySQL connector is GPL and so if you want to use it from a non-open-source application, you must apply for special permission. This was doable when Sun owned MySQL, but the process appears to be more complicated now that it's owned by Oracle. You must first sign up as an Oracle partner and their web site suggests a 'Gold' membership for driver integration which costs $2500 per year. It's not clear whether this is mandatory and whether your application will be considered with a free membership. I've also been unable to use their partner sign-up web page - it appears to be broken and they haven't responded to a query that I sent them on this. In short, $100 or so is looking very cheap for DevArt's connector.
6-month update: DevArt's connector has been working well and I continue to recommend it. And Oracle have confirmed to me that they require $2500 per year to permit use of their MySQL driver with non-open-source software.
MySQL used to have a Migration Toolkit, to make it easier to import from SQL Server and get started with MySQL as a production platform. That has been discontinued as a product. We were promised that an equivalent product would be added to the newer MySQL Workbench, but that has not happened.
It strikes me as a bizarre business decision, by the MySQL team, to put an extra barrier in the way of people who are considering moving from an MS-stack to a LAMP-stack.
Yes, migration toolkit was awesome.
But still they support the import/export in mysql workbench.
Checkout here:
http://dev.mysql.com/doc/workbench/en/wb-server-administration-manage-data-import-export.html
That seems like a strange move indeed...
You will find several tools suggested under "Migration Tools" here: dev.mysql.com/tech-resources/articles/migrating-from-microsoft.html.
You can migrate Data from MSSQL using PHPMyAdmin Web Interface!
Check here!
To install it on your LAMP-Stack (if you don't have it already), type this on server:
sudo apt-get install phpmyadmin
and Voilá!
:)
Latest MySQL moves look like the typical management decisions based upon marketing rather than actual software capabilities. The company has been through several owners in a few years and the last one, Oracle, has a strong will to make money out of it. (They are even making money out of Sun Microsystems!) MySQL used to have a bunch of poorly maintained GUI tools with a widely variable quality level. That's okay for most users but it scares away companies, which are the type of users that are willing to pay. Creating a single suite out of it looks like an intelligent move in the long term but they probably lack resources to speed up things and they want results now.
Right now, you can still find the old tools if you dig into the archives section from the download page. You'd better grab your copy before they change their mind. ;-)
I am starting a new client/server project at work and I want to start using some of the newer technologies I've been reading about, LINQ and Generics being the main ones. Up until now I have been developing these types of applications with MySQL as clients were unwilling to pay the large licence costs for MSSQL.
I have played around a small amount with the express versions but have never actually developed anything with them. The new application will not have more than 5 concurrent connections but will be needed for daily reporting.
Can MSSQL 2005 express still be downloaded? I cant seem to find it on the microsoft site. I would be hesitant to use MSSQL 2008 on a project so soon after its release.
Are the express version adequate for my needs, I'm sure loads of people reading this have used them. Did you encounter any problems?
The answer to the question on any project in regards to what platform/technologies to use is: What does everyone know best?
Yes express can still be downloaded.
Will it fit your requirements? That depends on your requirements, of course. I have deployed MSSQL2005 Express on several enterprise level projects which I knew had a fixed database size that would never be exceeded (Express has a limit of each database of 4Gb). Also keep in mind there are other hardware constraints such as a 1 cpu limit.
Another thing to consider is if you need the Enterprise level tools that come with a paid edition of SQL Server. If you are moving a lot of flat data around you are stuck writing your own Bulk Copy Procs, which rule the house, but its an extra step, no doubt.
Note sure about #2 but you can download SQL Server Express 2005 here.
Sql express has more features, and is a lot more powerful, but will only run on windows boxes. If you ever need to scale Sql express can be switched easily to a commercial variant.
MySql doesn't support half the features, but does have most of the basic ones you actually need, and will run on windows or *nix boxes. It's also not throttled in the same way as Sql express is.
In my opinion (having used both extensively, but not touched MySql for a few years) Sql express is a far better DB system. If you're building .Net applications the Linq support is a deal clincher.
If you aren't going for pure Sql server support, I wouldn't go for pure MySql support instead. Use a DBFactory design pattern to load your data layer or use simple SQL:92 syntax that's a lowest common denominator.
Why not go to Sql server express 2008?
I'm mostly going to advocate MS SQL Server because of .NET integration. Linq To Sql is pretty much my favorite way to do deal with databases these days: anonymous functions make everything better! My current place of work has also used MSSQL Express for real projects, so you have at least two of us confirming that the restrictions aren't too harsh.
I have about 50 web sites running perl/apache/mysql and about 10 running C#/ASP.Net/SQL Server (Lite) and other (large) applications running on SQL Server (Heavy). I never have problems with SQL Server - it just works. I often have problems with MySQL.
My advice would be to go for the SQL Server based option even if you had to pay for it.