How to run SQL on the deployment server local Oracle database.

Have you ever needed to connect directly to the local Oracle Planner database on the deployment server? Maybe you need to change server names or update the ESU list. It's actually pretty easy when you remember one simple step.

But first - Did you know that the planner database is a full version of Oracle Enterprise Edition (EE)? Yes, it's true. It does have a significant restriction though: You can only use it for the E1 planner database. If you want to put anything on that database that is not the planner metadata you will have to pay $47,000 for a full EE license.

Now, how do you get logged in to the local Planner database to run some SQL? To get started, let's try logging in to a planner DB without doing anything special. Open a command window and enter the following command:

sqlplus / as sysdba

In this example, the ORA-01031 error means you are not in the Windows “Oracle DBA Group”. To fix this, you need to add your user to the group. Open up Server Manager and go to Configuration/Local Users and Groups/Groups.

Find the group ora_dba and double click it:

In there click Add, find your name, and click OK. You’ll see your name in the Members: list now. Click OK

Close out of the command window you were using before and open a new one. Try to connect to sqlplus again:

There you go! You’re now connected to the planner database.

ORACLE 11g IS DEAD! LONG LIVE 12c!

At the end of this year, the Oracle 11.2.0.4 database goes on Extended Support. 11.2.0.3 hits extended support on August 27th - less than one month away! 11.2.0.1 and 2 are completely out of support.

For 11.2.0.3 and .4, clients cannot get support or bug fixes after Extended Support ends unless they purchase additional coverage. There is no such option for lower releases.

That's not all. Oracle 12c is only supported as of the 9.1.4 E1 tools release. If a client is on 11g and wishes to go to 12c, they also have to be at that TR or higher.

I know many companies are running 11g and don't know that the database is going off of support. For the ones that do know of their impending doom, some are making plans to upgrade without considering the tools release they're currently on.

Are you going to have problems if you don't upgrade all the things? I've got good money on "no". My theory on upgrades and patches is that you should only do it if you have a need. A need for new functionality or a need to patch something. Otherwise if everything is running fine why go through the trouble?

Still, most companies don't like the idea of running out-of-date or unsupported software. With the various deadlines approaching fast, now is a good time to sell some upgrades. Whether you're selling to a client or just to your own boss, you better get on it before the end of support. Better to forewarn people than trying to explain why you didn't say anything prior to the deadline.