When you connect from ODI Studio 12c to the repository you may get error “no ocijdbc in java.library.path”. In my case I use ODI Studio 12c installed on Windows 7 64bit machine and connecting to ODI 12c linux environment. So why do I get this error?
On the same note I use Oracle JDBC Driver ODI driver connection. As the studio does not use the tnsnames to connect to the Oracle instance if you try jdbc:oracle:oci8:@<tns_alias> it will not work. That’s why you can give (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=SID))) instead. So far so good but still get the same error.
This error gives me a signal it might be because of incompatibility of the jdbc drivers coming with ODI 12c and the Oracle client. As a starting point I have Oracle 22.214.171.124 client installed on my station. Let’s check what version ODI 12c uses, probably 12? Check this in <<ODI_HOME>>\oracle_common\modules\oracle.jdbc_12.1.0\ojdbc6dms\META-INF\MANIFEST.MF
Now it makes perfect sense. Let’s install Oracle 126.96.36.199.0 client. Once this is done two more things needed. Add the following line in <<ODI_HOME>>\odi\studio\bin\odi.conf\odi.conf
The second thing is to set the system variables for
Enjoy ODI 12c world!
Happy New Year everyone. I wish you a prosperous 2015!
Time is passing by too fast. I had a dynamic 2014 with a couple of interesting projects. It’s not time to recap now but it is definitely time to refresh my blog.
For me with the new year comes the new beginning too. I switched from contracting to permanent job because I’ve always wanted to work for an Oracle partner in the UK with big Oracle projects. I am very pleased I joined Peak Indicators as a BI Consultant to work on OBIEE and ODI projects. Peak Indicators is an experienced Business Intelligence consulting company which is an Oracle Gold Partner highly specialized in Oracle Business Intelligence.
I had a trip to Chesterfield to meet the colleagues there and some in London. I am glad that a week after I started I had the chance to install OBIEE and apply latest OBIEE bundle patch (188.8.131.52.150120) released this Tuesday. So I started to get the feel of it and I would say there is a lot to crunch. I hope I will be able to blog more and attend UKOUG as well as BGOUG.
I think I am a little bit late but on the other hand it’s never too late to comment and share opinion about some among the 500+ new features introduced with Oracle Database 12c.
The first feature which really caught my attention was Multiple Indexes on Same Set of Columns as long as there are differences and only one of them is visible. Before getting into an example , there are some exceptions Oracle Doc :
- You cannot create a B-tree index and a B-tree cluster index on the same set of columns.
- You cannot create a B-tree index and an index-organized table on the same set of columns.
Prior to 12c you know when you try to create more than one index on the same list of columns you get ORA-01408: such column list already indexed error.
If you think, it sounds quite logical. What is that which made this feature be available in Oracle Database 12c now? This is Testing performance and more important Index availability. Now index maintenance and respectively application maintenance is much easier.
Imagine you have to change an existing index(even more a large index)from a non-partitioned index to a partitioned index or convert a B-Tree to a Bitmap index. Instead of having ‘downtime’ and wait for the existing index to be dropped and the set of columns will not be covered by the index. We can create the new one in advance, test and when satisfied make invisible the existing one(or drop it) and make visible the newly created index. Flexible, isn’t it !?!
SQL*Plus: Release 184.108.40.206.0 Production on Mon Jul 29 11:09:01 2013 Copyright (c) 1982, 2013, Oracle. All rights reserved. SQL> create table test_idx ( col1 integer, col2 integer, col3 integer, col4 varchar2(100) ); Table created. SQL> create index idx1 on test_idx(col1,col2,col3); Index created. SQL> create bitmap index idx2 on test_idx(col1,col2,col3); create bitmap index idx2 on test_idx(col1,col2,col3) * ERROR at line 1: ORA-01408: such column list already indexed SQL> create bitmap index idx2 on test_idx(col1,col2,col3) invisible; Index created.
We can now test idx2 index and if it performs well drop idx1 and make idx2 visible. There are a bunch of articles already about this new feature, have a look at Tom Kyte’s Blog and Richard Foote’s Blog .
Next, I’d like to mention DEFAULT values using sequences. It is quite handy to have CURRVAL and NEXTVAL as the default values for a column:
SQL> create sequence s_test_seq; Sequence created. SQL> create table test_seq (col1 NUMBER DEFAULT s_test_seq.NEXTVAL, 2 col2 varchar2(100) ); Table created. SQL> insert into test_seq(col2)values('Test Default value'); 1 row created. SQL> commit; Commit complete. SQL> select * from test_seq; COL1 COL2 ========== ===================================== 1 Test Default value
This means that the trigger-based functionality and writing PL/SQL for populating number id columns with a sequence is now a past with Oracle 12c.
You can also check Tim Hall’s blog for more details.
Other features which impress me at first glance are:
- Oracle Data Redaction
- Online Statistics Gathering for Bulk Loads
- Dynamic Statistics
- Concurrent Statistics Gathering
- Concurrent Execution of UNION and UNION ALL Branches
- Automatic Data Optimization
- Move a Data File Online
- ONLINE Move Partition
- Table-Level Recovery From Backups
- Oracle Data Pump Export View As a Table
- Partial Indexes for Partitioned Tables
- SYSBACKUP Administration Privilege
- Last Login Time Information
- Real-Time Database Operations Monitoring
- Enhanced Online DDL Capabilities(no longer require blocking locks)
- Row Limiting Clause for Top-N Queries
- Synchronous Materialized View Refresh
Just a quick mention when you get the error bellow while trying to create a trigger for example:
CREATE OR REPLACE TRIGGER AGE_GROUP_TRG
BEFORE INSERT ON AGE_GROUP REFERENCING
NEW AS NEW
FOR EACH ROW
SELECT AGE_GROUP_SEQ.nextval INTO :NEW.AGE_GROUP_ID FROM dual;
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [kqlidchg1], , , , , , , , , , , 
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.I_PLSCOPE_SIG_IDENTIFIER$) violated
00603. 00000 – “ORACLE server session terminated by fatal error”
*Cause: An ORACLE server session is in an unrecoverable state.
*Action: Login to ORACLE again so a new server session will be created
The root cause is in the plscope_settings. If you use SQL Developer try to change PLSCOPE_SETTINGS to NONE from menu Tools->Preferences->Database->PL/SQL Compiler->PLScope Identifiers.
There are quite a lot discussions about this like this thread.
This post is about to quickly refer to one of the most common trick you must know when you install ODI 11g on Windows Server 2008 64 bit OS.
64-bit JDK is just fine but once you start ODI 11g Studio from the same machine you will get “Oracle ODI 11g Unable to launch the Java Virtual Machine Located at path …”:
This is because ODI 11g Studio client tool works only with 32-bit JDK. The workaround is to edit $ODI_HOME\oracledi\client\odi\bin\odi.conf and point SetJavaHome to the 32-bit path.
You also can have a look here.
These days I configured Oracle OSWatcher tool and yast package for EM Grid Control used to manage and monitor Oracle servers. I want to share how quickly to configure and start using them on Linux.
OSWatcher invokes system utilities like ps, top, iostat, vmstat, netstat and collects data according to the specified parameters. You can download it from Metalink.
unzip it to OSWatcher directory you would use($OSWATCHER_HOME)
tar -xvf oswbb4.0.tar
OSWatcher has been renamed to OSWatcher Black Box to avoid the confusion with the too many tools with this name. OSWatcher Black Box Analyzer(OSWbba ) is a graphing and analysis utility which comes bundled with OSWbb v4.0.0 and higher. For OSWbba you need java version 1.4.2 or higher.
Put next lines in the profile needed by OSWatcher:
alias oswatch=’java -jar $OSWATCHER_HOME/oswbba.jar -i $OSWATCHER_HOME/archive’
Let’s start it with nohup in background and configure to take snapshots with the system utilities at every 5 minutes for the last 24 hours.
nohup ./startOSWbb.sh 300 24 &
What it does is subdirs in $OSWATCHER_HOME/archives like oswiostat, oswmeminfo, oswmpstat, oswnetstat, oswprvtnet, oswps, oswslabinfo, oswtop, oswvmstat where result .dat files with collected data for each hour reside. OSWbba parses all the archive files and you invoke it from the alias created in the profile:
Starting OSW Black Box Analyzer V4.0
OSWatcher Black Box Analyzer Written by Oracle Center of Expertise
Copyright (c) 2012 by Oracle Corporation
Parsing Data. Please Wait…
Parsing file …iostat_12.02.16.0100.dat …
Parsing file …vmstat_12.02.16.0100.dat …
Enter 1 to Display CPU Process Queue Graphs
Enter 2 to Display CPU Utilization Graphs
Enter 3 to Display CPU Other Graphs
Enter 4 to Display Memory Graphs
Enter 5 to Display Disk IO Graphs
Enter 6 to Generate All CPU Gif Files
Enter 7 to Generate All Memory Gif Files
Enter 8 to Generate All Disk Gif Files
Enter L to Specify Alternate Location of Gif Directory
Enter T to Specify Different Time Scale
Enter D to Return to Default Time Scale
Enter R to Remove Currently Displayed Graphs
Enter P to Generate A Profile
Enter A to Analyze Data
Enter Q to Quit Program
Please Select an Option:
Yast(Yet Another Setup Tool) is needed if you need to administer a linux host through Enterprise Manager Grid Control. Download yast from here.
tar -xvf yast_el5_x86_64.tar
Start it in the commandline:
Here is how it looks like in EM Grid Control:
Still in Oracle 220.127.116.11 may appear an alert in EM related to metric “Generic Operational Error”. Occasionally when running Automatic SQL Tuning the following messages may appear in the alert log:
Process 0x%p appears to be hung in Auto SQL Tuning task
Current time = %u, process death time = %u
Attempting to kill process 0x%p with OS pid = %s
OSD kill succeeded for process 0x%p
You can have a look at “How to Avoid or Prevent Hung Auto Tuning Task Messages [ID 1344499.1]” in Metalink and this post .
The explanation is that the AUTO SQL TUNING TASK has been over-running and as a protective measure it is auto killed. As thus, there is no fix for this and the solution is to disable this job and eventually manually execute it when needed. Here is how to do that:
client_name => ‘sql tuning advisor’,
operation => NULL,
window_name => NULL);
The Automatic SQL Tuning :
SELECT TASK_NAME, DESCRIPTION, STATUS, LAST_MODIFIED FROM DBA_ADVISOR_TASKS
WHERE task_name LIKE ‘%AUTO_SQL_TUNING_TASK%';
is part of the Automated Maintenance Tasks together with Optimizer Statistics Gathering and Segment Advisor. You can see this also in Oracle EM Grid Control->Server->Automated Maintenance Tasks.
I have a similar post but the error in the alert log is different.