Managed Services

Don’t Be Left in the Dark – Zero downtime during hurricane Sandy

Author: Kyle Snyder Date: November 1st, 2012
Categories: Managed Services

Not even the largest "super storm" in the history of the East Coast can leave BizTech's hosting customers in the dark.  

» Read More

How to rename an Oracle Database

Author: Raj Ravikumar Date: May 28th, 2012
Categories: Managed Services

Oracle database’s ORACLE_SID can be renamed using a couple of methods. The first method, which is a tradition method, is to create a new control file using the reuse database flag and give it a new incarnation. Once this is done we can change the values in the external files (sqlnet.ora, tnsnames.ora, init.ora (spfile)) and open the database. From Oracle 9i and beyond Oracle database can be renamed using the dbnewid (or) nid utility. In this post, we will go through the steps to rename the database using the nid utility. 

» Read More

Hyperion Business Rules (HBR) is de-supported in EPM 11.1.2.2

Author: Raj Ravikumar Date: May 17th, 2012
Categories: Managed Services

Oracle has de-supported Hyperion Business Rules (HBR) in the 11.1.2.2 release. Customers with HBR in the previous releases need to migrate them to Calc Manager in 11.1.2.2 

» Read More

Resetting Lost Oracle WebLogic Password for Fusion Middleware Applications

Author: Raj Ravikumar Date: May 10th, 2012
Categories: Managed Services, Oracle Application Services, Oracle Business Intelligence

When Fusion Middleware Applications are installed there is a default user (weblogic or a specific name that you provide) that is created during the domain creation which acts as a super user for all Middleware Applications. This post walks through the process of resetting the weblogic password in an event that it’s lost.  

» Read More

Oracle EBS ATG Seed Data Comparison Report

Author: biztech_admin Date: June 30th, 2011
Categories: E-Business Suite, Managed Services, Oracle Application Services

Oracle finally released a reporting tool that reports on the differences in E-Business Suite database objects between one release and another. That's a very useful reference to Tech users to understand EBS dictionary at a module level, but EBS defaults are delivered as seed data within the database objects themselves. What about the differences in this seed data between one release and another?  

» Read More

Disaster Recovery and Business Continuity

Author: biztech_admin Date: March 28th, 2011
Categories: Managed Services

Disaster Recovery (DR) is the process an organization uses to recover access to their data, software,  hardware that are needed to resume business critical applications after the event of either a natural disaster or planned caused by humans. When a disaster occurs, the Disaster Recovery plan’s aim is to restore an acceptable level of operations with an acceptable recovery time objects. The overall goal of a Disaster Recovery plan is to minimize downtime in the event a disaster occurs.

Disaster Recovery Plans are generally part of a larger, more extensive practice known as Business Continuity Planning. DR plans should be well practiced so that the Business owners are familiar with the specific actions they will need to take should a disaster occur. DR plans must also be adaptable and routinely updated. Apart from the business critical applications availability, The most important component is human capital which is often overlooked by most corporations. Companies tend to assume that their staff will always be available. When a disaster occurs, sickness, disability of a key employee, or even a death, can have a devastating effect on a business. Business needs and the threats to business are constantly changing. New Customers, and software applications as well as changes to Infrastructure components affect Disaster Recovery plan. It is a good practice to update Disaster Recover Plans anytime a significant change is made to critical business process or the IT infrastructure that supports them. At a minimum, its recommended to test and update disaster Recovery plans on an annual basis.

Disaster Recovery Plan – 101

• Establish Recovery Time Objectives (RTO’s) and the necessary Infrastructure to achieve them.
• Define Disaster Recover Roles and Responsibilities
• Have a Disaster Recovery Communication Plan that details procedure for the activation of the Recovery team.
• Have Detailed Disaster Recover Procedures
• Validation of technical and personnel readiness
• Define Recovery Time Objectives and Recovery Point Objectives
• Testing and verification of technical recovery capabilities at least twice a year, and a team preparedness exercises at least annually.
• A comprehensive plan for providing end users access to systems, irrespective of how  networks and hardware may be impacted by Disaster.