Welcome to Datavail’s Blog, where you can read the latest insights, tips and opinions of our experts on all things data and technology.
As an Oracle Apps administrator, it’s a good idea to have a punch list of things to check after your applications have been started, to ensure all services are working correctly.
A while back I was working with a client on a web application project that had a basic SQL Server database as the relational data storage system.
We’ve been doing quite a bit of Hyperion Essbase integration into Oracle BIEE lately. It is just cool stuff and most Oracle BI consulting groups will admit that this is all the rave right now.
Your E-Business Suite session is idle, and in your haste you simply click the ‘X’ at the top of your browser. You know it’s not the proper thing to do, but you’re not sure of the implications.
Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.
We all know proactive service when we see it. A couple of examples: Proactive is when you are shopping for a new gadget, but just before you buy it the clerk tells you a special battery is required (even though the box fails to mention it) but is not included. “Would you like one of those as well?”