ODI Installation Issue :

You Can Install any number of ODI version in your System:
Example you can install below two version in your machine.
ODI 11G Version(11.1.1.5)   and
ODI 11G Version(11.1.1.6)

The other ODI version will come under   Start-->All Program-->Oracle-->Oracle Data Integrator(2)-->ODI

Issue 1:
I'm running Windows 7 64-bit and have a 64-bit installation of JDK 1.6 installed. I installed the generic version of ODI Studio 11g (11.1.1.5) (the 32-bit version will not install on Windows 64-bit).

After the installation and launching ODI Studio, I received the following error:

Unable to launch the Java Virtual Machine Located at path:
c:\Progra~1\Java\jdk1.6.0_26\jre\bin\server\jvm.dll

Solution -1:

1. Download and install the 32-bit version of JDK 1.6 (not the 64-bit version!):

http://download.oracle.com/otn-pub/java/jdk/6u31-b05/jdk-6u31-windows-i586.exe

2. Edit the odi.conf file which is located here:

C:\Oracle\[your_install_directory]\oracledi\client\odi\bin\odi.conf

3. Locate and make the following change:

OLD (which is pointing to the 64-bit JDK):
SetJavaHome C:\Program Files (x86)\Java\jdk1.6.0_26

NEW (change it to point to the 32-bit JDK):
SetJavaHome C:\Program Files (x86)\Java\jdk1.6.0_31

4. Launce ODI Studio 11g again 

Solution 2:

1.Install jdk1.7.0 in C:\Java\jdk1.7.0   drive then change the below path                                    C:\Oracle\[your_install_directory]\oracledi\client\odi\bin\odi.conf           Change in SetJavaHome c:/Java/jdk1.7.0

ODI(Oracle Data Integrator)11G Installation Steps

ODI(Oracle Data integrator) 11G Installation for 64 bit:

Step1:
Install the Java in C: \Java  in your local machine.You can Download jdk-7u17-windows-x64 files from internet or from Oracle Site.
Please verify ,after installation java, a folder will create in C:\Program File\Java\jdk1.7.0_17 path. 

Step3:
Go to -->Disk1\install\win64 and click on setup, it will ask for a JDK location.After click on win64  a cmd(command prompt) window will open.

Step3: 
Provide  the path up to jdk1.7.0_17 folder and press enter Example:C:\Program Files\Java\jdk1.7.0_17)

Step4: After Completing Step 4 it will open up the "Welcome" Screen of Oracle Data Integrator. CLICK --Next

Step 5:Screen Name: Install Software Update                                                                                Select Option "Skip software Updates" button

Step6: Screen Name: Select Installation Type                                                                            Select Option "Developer installation" and "Standalone Installation" CLICK--Next

Step7: Screen Name:Prerequisite Checks     CLICK--Next

Step:8: Screen Name:Specify Installation Location                                                                            Provide Installation Location    CLICK--Next

Step9: Screen Name :Repository Configuration                                                                                  select option  "Skip Repository Configuration"     CLICK -->Next

Step10: Screen Name :Specify Agent Details                                                                                           Agent Name: "PowerAgent"                                                                                                                Agent Port:"7002"                         CLICK --Next

Step11: Screen Name:"Specify Security Updates"                                                                                 Un-check "I wish to receive security updates via my oracle support"   CLICK--Next

Step12: Screen Name:"Installation Summary"     CLICK-->Install

Step13: Screen Name:"Installation Progress"  CLICK--Next

Step14: Screen Name:"Configuration Progress" CLICK--Next

Step15: Screen Name:"Configuration Progress"  Uncheck "ODI Configuration" CLICK--Next

Step 14: Screen Name:"Installation Completed" CLICK--Finish

Now we can see the installation was successful.

Final Step:GO to Start--->All Programs----->Oracle----->Oracle Data Integrator ----->ODI Studio.

Above step will opens the starting page Oracle Data Integrator.

Oracle Warehouse Installation Basics

Oracle Warehouse Installation Basics Information:

If  you want to work on all Oracle BI Component then you must have install below software in your Local Machine.
1.ODI(Oracle Data Integrator) 11G.
2.SQL Developer.

3.Oracle 11G(if required). Oracle Data base is very heavy and not advise  to install in your machine(It Required 6 to 8 GB RAM)Always install  oracle Database on separate server,and then from your machine you can connect to oracle server.

4.Oracle 11G XE(Express Edition): ( If you feel Oracle 11G Data base is slow your system then you  can install Oracle 11g XE (express edition with limited functionality that will be fine for practice/Training Purpose). This occupies less space and it will not use more system resources.

5.OBI:Not recommended to install OBI on local system  as it occupies more space.Install OBI in Separate server

ODI(Oracle Data Integrator)

Introduction to Oracle Data Integrator:
 

1.ODI(Oracle Data Integrator) is a Widely used data integration software product.
2.ODI Provides a new design approach to Defining data transformation and integration process and provide results with faster and simpler development and maintenance.
3.ODI is based on unique E-LT architecture (Extract - Load Transform),
4.It Provides high performance for execution of data transformation and validation process and it is very cost effective.

Why to choose ODI:
•Faster and simpler development and maintenance: The declarative rules driven approach to data integration greatly reduces the learning curve of the product and increases developer productivity while facilitating ongoing maintenance.
 
•Data quality firewall: Oracle Data Integrator ensures that faulty data is automatically detected and  recycled before insertion in the target application. This is performed without the need for programming, following the data integrity rules and constraints defined both on the target application  and in Oracle Data Integrator.

•Better execution performance: traditional data integration software (ETL) is based on proprietary  engines that perform data transformations row by row, thus limiting    performance. By implementing  an E-LT architecture, based on your existing RDBMS engines and SQL, you are capable of executing data  transformations on the target server at a set-based level, giving you much higher performance.

Simpler and more efficient architecture: The E-LT architecture removes the need for an ETL Server sitting between the sources and the target server. It utilizes the source and target servers to perform complex transformations, most of which happen in batch mode when the server is not busy processing end-user queries.
•Platform Independence: Oracle Data Integrator supports all platforms, hardware and OSs with the same software.

Data Connectivity: Oracle Data Integrator supports all RDBMSs including all leading Data warehousing platforms such as Oracle, Exadata, Teradata, IBM DB2, Netezza, Sybase IQ and numerous other technologies such as flat files, ERPs, LDAP, XML.

• Cost-savings: the elimination of the ETL Server and ETL engine reduces both the initial hardware and software acquisition and maintenance costs. The reduced learning curve and increased developer productivity significantly reduce the overall labor costs of the project, as well as the cost of ongoing enhancements.

What is NOLOCK Hint in SQL server ?

Using the NOLOCK query optimiser hint is generally considered good practice in order to improve concurrency on a busy system. When the NOLOCK hint is used in a SELECT statement, no locks are taken when data is read. The result is a Dirty Read, which means that another process could be updating the data at the exact time you are reading it. There are no guarantees that your query will retrieve the most recent data.  SELECT statements take Shared locks, means multiple SELECT statements are allowed simultaneous access, but other processes are blocked from modifying the data. The updates will queue until all the reads have completed, and reads requested after the update will wait for the updates to complete. The result to your system is delay(blocking).

The slight disadvantage is that one may not be sure that they are getting the data which is currently being updated in the Table ie Without lock protection, you cannot be guaranteed that the data isn’t changing during the time that the query is running.


How to use:
SELECT * FROM TableName (NOLOCK)

Steps to Deploy Report Model Into Production Server.

 Note :

1.First Deploy the .smdl File into Local Server(http://localhost/reportserver) and then download the .smdl file in to folder(send downloaded files as a deliverable).

2.All tables related with report model should be present  in the data base.

1.Create the DataSource inside the "data Source" folder

                1.1 Click On "New data Source" tab.

                1.2 Give the New data Source Name(.dsv)

                1.3 Data source type: microsoft sql server

                1.4 Connection String:Data Source=<machine name>;Initial Catalog=<db name>;

                Example:Data Source=A648;Initial Catalog=database_Name;

                1.5 check Windows integrated security.

                1.6 Test connection.

                1.7 Apply

2.GO to "Models" Folder

               2.1 Upload the .smdl file

               2.2 Right click-->Manage-->Data Source-->browse the data source.

              2.3 select the data source inside the "data source"Folder.

3.Upload the RDL File.

               3.1 Right click-->Manage-->Data Source-->browse the shared data source.

               3.2 select the data source inside the "Model"Folder.

Error,while restoring the database in MS SQLserver 2008R2

Error: “The file “C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\mastlog.ldf” is compressed but does not reside in a read-only database or file group. The file must be decompressed.”

solution1:Opened my mdf file properties dialog box, and in the advance tab the problem was revealed: the “compress content” checkbox was checked.

After unchecking and saving changes, SQL Server accepted the attach with no problem whatsoever.

solution2:Check the drive where data base is going to restore.Right click the Drive(C: Drive)--> Property-->General-->Compress this drive to save the disk space(it should be unchecked )