Storage Engines Feature Summary

^[a] InnoDB support for geospatial indexing is available in MySQL 5.7.5 and higher.

^[b] InnoDB utilizes hash indexes internally for its Adaptive Hash Index feature.

^[c] InnoDB support for FULLTEXT indexes is available in MySQL 5.6.4 and higher.

^[d] Compressed MyISAM tables are supported only when using the compressed row format. Tables using the compressed row format with MyISAM are read only.

^[e] Compressed InnoDB tables require the InnoDB Barracuda file format.

^[f] Implemented in the server (via encryption functions), rather than in the storage engine.

^[g] Implemented in the server, rather than in the storage engine.

^[h] Implemented in the server, rather than in the storage engine.

Here the issue that I have found during the clone DB tier:

AutoConfig could not successfully execute the following scripts:

    Directory: /clone/oracle/product/11.2.0/perl/bin/perl -I /clone/oracle/product/11.2.0/perl/lib/5.8.3 -I /clone/oracle/product/11.2.0/perl/lib/site_perl/5.8.3 -I /clone/oracle/product/11.2.0/appsutil/perl /clone/oracle/product/11.2.0/appsutil/clone

ouicli.pl               INSTE8_APPLY       255

AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.

Action Plan:

1.  Change the DB CONTEXT_FILE PERL5LIB  parameter from 5.8.3 to 5.10.0

2.  Change the $ORACLE_HOME/appsutil/template/adxdbctx.tmp as well as env file.

3. Run autoconfig on DB node

4. Run adpreclone procedure on DB tier

5. Copy the data to clone instance and rerun adcfgclone.

In This new version there is a new environment variable called $INST_TOP.

This variable stand for the top level of the Application.

This main directory contain all of the configuration files of the applications ( SSL files,log/out files, scripts act…)

One of the major benefits is that the AD utilities ( adpatch, adadmin act….) while running writing there logs to the new $INST_TOP only.

And As a outcome from that we can grant read-only to the rest of the application this option is gaining the security of our environment.

The new $INST_TOP is allowing us to easily manage and administer the application tier by the separating the configuration  files from the application files.

By dividing the EBS environment to the applicative and administrative part we can share code between different environments  like DEV, TEST, PATCH act…

Big Data technologies have been all over technology press for what seems like a long time now. MongoDB is an established player in the space, one of the first examples of what have come to be called ‘NOSQL’ databases. With its schema-less design MongoDB is well suited to storing unstructured data and it promises many features to make it easy to scale across multiple servers. MongoDB version 2.6 also introduced support for full text indexing and search.

With our traditional expertise being with kdb+, we decided to look at ways the two (kdb+ and MongoDB) technologies might complement each other. kdb+ excels with time series data analysis with structured data, while MongoDB offers text indexing and search functionality that doesn’t yet have an equivalent in kdb+

For this case study, we’re using MongoDB as the text storage for a kdb+ database – offloading the storage of large text documents from the main kdb+ server, taking advantage of Mongo DB text indexing for searching, while retaining the speed of kdb+ for searches and reporting on the structured data.

mongoq

mongoq is a set of libraries built on top of the mongo c driver, to allow access to a MongoDB database direct from q. The C functions take json strings as parameters, which are converted to bsondocuments by libbson prior to being passed to MongoDB. Result sets are converted from bson to json and returned from C to q as a list of json strings.

Some wrapper q functions are provided which take dictionary parameters, handling json encoding and decoding using j.k

Source code, documentation and examples can be found on our github site here. The interface is in POC/alpha state at the moment – mongo c driver API coverage isn’t complete yet, and there are performance improvements and better error handing planned in the near future.

Reddit Database

For a dataset for our case study, we found 1Gb of reddit comments on this thread.

Loading

We used a q script to parse the data, maintaining the meta data in a kdb+ splayed table, with any long strings (comment text, topic, comment html) being pushed to MongoDB, referenced with a MongoDB id in the kdb+ table.

The loader script outputs the following, including a breakdown of the timings:

> q examples/comments_load.q mydb comments.all.sql
...
Processing - 1020 of 1048 MB : 97.4%
Processing - 1029 of 1048 MB : 98.3%
Processing - 1039 of 1048 MB : 99.2%
Processing - 1047 of 1048 MB : 100%
#####################################
# reading    | 0D00:00:00.743248000 #
# parsing    | 0D00:02:31.920447000 #
# mongoinsert| 0D00:03:13.843763000 #
# kdbwrite   | 0D00:01:40.621209000 #
# mongoindex | 0D00:02:31.501243000 #
# TOTAL      | 0D00:09:58.629910000 #
#####################################

Free text data always presents a parsing challenge, and this data has been imported to a sql database, then exported to text again, so the escaping of special characters is inconsistent. We’ve chosen to process the .sql file instead of the .csv as it’s easier to tell apart genuine record breaks from newlines inside comments. We aren’t going to have 100% success rate at processing every post into the correct table structure, but the script should recover within a record or two if it’s thrown off by the content of a post.

The following code is where the loader script writes to the two databases, MongoDB via the mongoq library, and kdb+ appending to a splayed table on disk

processdata:{[t]
  mgcols:`link_title`subreddit`body`body_html`author_flair_text;
  oid:.mg.add[`comments;mgcols#t];
  (` sv db,`comments`) upsert .Q.en[db] (mgcols _ t),'([]mgid:oid);
 };

The .mg.add function takes a table or list of dictionaries as a parameter, and returns a vector of MongoDB _id values as a 16 byte GUID type.

This id can be used for retrieval:

q)id:.mg.add[`test;([]time:12 13t;sym:`xx`yyy;price:11.2 34.5)]
q)id
00000000-54f6-4410-dfa8-3258b51290e8 00000000-54f6-4410-dfa8-3258b51290e9
q).mg.find[`test;id;()] / all fields for these ids in 'test' collection
time           sym   price
--------------------------
"12:00:00.000" "xx"  11.2
"13:00:00.000" "yyy" 34.5

Text Index

MongoDB has a text indexing feature which supports stemming and relevance scoring. We’re going to use this feature as it provides functionality not readily available in q. The mongoq interface includes an ‘addindex’ function which accepts index parameters as a json string. To create a text index on the ‘body’ field in the comments records we’re storing, we do the following at the end of the loader script:

.mg.addindex[`comments;.j.j enlist[`body]!enlist `text]

To index across all text fields (`$”**”) can be used in place of the field name.

Queries

The following are some example queries and their execution time on our machine. Queries which ship large amounts of data to or from from Mongo will be slowed down by the extra step in the bson<->json<->kobject conversion – this would ideally be replaced with a direct bson<->kobject conversion library.

TOP 10 TOPICS FOR SEARCH TERM

q)topics:{[term] 10 sublist select score, subreddit, title:40 sublist' link_title from `score xdesc 0!select max score, first subreddit by link_title from .mg.search[`comments;term]}
q)\t topics "IBM"
63
q)topics "IBM"
score    subreddit          title
----------------------------------------------------------------------
0.963724 "todayilearned"    "TIL that Bill Gates told the creators of"
0.904494 "linux"            "Anybody know a bit about older keyboards"
0.803571 "starcraft"        "Why, and how much, do Blizzard invest in"
0.779412 "gamecollecting"   "Looking for a SEGA Saturn Keyboard."
0.765306 "Bitcoin"          "Seeking Alpha''s AJ Watkinson Predicts a"
0.761811 "buildapc"         "What is the major differance between Int"
0.760274 "linux"            "Linux Desktop''s Missed Opportunities"
0.75     "learnprogramming" "Is anyone here familiar with Assembly? I"
0.666667 "apple"            "Apple''s iPhone, iPad used to place over"
0.583333 "Games"            "FIFA Manager series cancelled"

THREADS AND COMMENTS AGGREGATED BY SUBFORUM FOR SEARCH TERM

q)threads
{[term]
  t:comments comments[`mgid] bin m:.mg.searchid[`comments;term];
  t:(`$.mg.find[`comments;m;`subreddit]),'t;
  r:`threads xdesc select threads:count distinct link_id, comments:count i by subreddit from t;
  r}
q)threads "\"ivy bridge\"" / search exact term
subreddit      | threads comments
---------------| ----------------
buildapc       | 9       9
gaming         | 2       3
pcmasterrace   | 2       2
AskReddit      | 1       1
WildStar       | 1       1
battlestations | 1       1	
buildapcforme  | 1       1
buildapcsales  | 1       1
dayz           | 1       1
hardware       | 1       1
linux          | 1       1
mcservers      | 1       1
programming    | 1       1
techsupportgore| 1       1

Conclusions

• MongoDB presents an interesting proposition as a text store backing to a kdb+ database, opening up search features that wouldn’t be easily replicated in a kdb+ only database
• Performance of the adaptor is acceptable as long as the amount of data passed between MongoDB and kdb+ is minimised. Future versions of the adaptor will skip the expensive json translation step with a direct bson<->kobject translation library
• All the adaptor code used for this post is available as open source on our github site. It should be considered in alpha state – report bugs and feature requests through github

It was done on 11.2.0.4 database and valid for other release

1. Remove Oracle Application Express:
?/apex/apxremov.sql
drop PUBLIC SYNONYM HTMLDB_SYSTEM;
drop PUBLIC SYNONYM HTMLDB_SYSTEM;

select comp_id, comp_name, version, status from dba_registry where comp_id=’APEX';

2.  Remove Oracle Workspace Manager Components:
@?/rdbms/admin/owmuinst.plb

select comp_id, comp_name, version, status from dba_registry where comp_id=’OWM';

3. Remove Enterprise Manager:
ALTER SYSTEM ENABLE RESTRICTED SESSION;
EXEC sysman.emd_maintenance.remove_em_dbms_jobs;
EXEC sysman.setEMUserContext(”,5);

DECLARE
CURSOR c1 IS
SELECT owner, synonym_name name
FROM dba_synonyms
WHERE table_owner = ‘SYSMAN';
BEGIN
FOR r1 IN c1
LOOP
IF r1.owner = ‘PUBLIC’ THEN
EXECUTE IMMEDIATE ‘DROP PUBLIC SYNONYM ‘||r1.name;
ELSE
EXECUTE IMMEDIATE ‘DROP SYNONYM ‘||r1.owner||’.’||r1.name;
END IF;
END LOOP;
END;
/

DROP USER mgmt_view CASCADE;
DROP USER sysman CASCADE;
DROP ROLE mgmt_user;

select comp_id, comp_name, version, status from dba_registry where comp_id=’EM';

4. Uninstalling Oracle Spatial:
shutdown immediate
startup

–Script
set pagesize 0
set feed off
spool drop_spatial.sql
select ‘drop public synonym “‘ || synonym_name || ‘”;’ from dba_synonyms where table_owner=’MDSYS';
spool off;
@drop_spatial.sql
commit;

shutdown immediate
startup

drop user MDSYS cascade;

select comp_id, comp_name, version, status from dba_registry where comp_id=’SDO';

SELECT object_name,object_type,owner FROM dba_objects WHERE status = ‘INVALID';

@$ORACLE_HOME/rdbms/admin/utlrp.sql

5. Remove Oracle Multimedia:
drop user ORDSYS cascade;
drop user ORDPLUGINS cascade;
drop user SI_INFORMTN_SCHEMA cascade;

–Script:
set pagesize 0
set feed off
spool drop_ordim.sql
select ‘drop public synonym “‘||b.object_name||'”;’ from dba_synonyms a, dba_objects b where b.status=’INVALID’
and b.object_type=’SYNONYM’
and b.owner=’PUBLIC’
and a.synonym_name=b.object_name
and a.table_owner not in (select username from dba_users);
spool off;
@drop_ordim;
commit;

select comp_id, comp_name, version, status from dba_registry where comp_id=’ORDIM';

SELECT object_name FROM dba_objects WHERE status = ‘INVALID';
@$ORACLE_HOME/rdbms/admin/utlrp.sql

6.  Remove Oracle Rules Manager:
@?/rdbms/admin/catnorul.sql
drop FUNCTION EXFSYS.RLM$WLNCHK;
@?/rdbms/admin/utlrp

select comp_id, comp_name, version, status from dba_registry where comp_id=’RUL';
SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

7.  Remove Oracle Expression Filter:
@?/rdbms/admin/catnoexf.sql

select comp_id, comp_name, version, status from dba_registry where comp_id=’EXF';
SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

8. Remove Oracle XML Database:
@?/rdbms/admin/catnoqm.sql
@?/rdbms/admin/catmeta.sql
@?/rdbms/admin/catpprvt.sql
@?/rdbms/admin/utlrp

drop FUNCTION AWM_CREATEXDSFOLDER;
drop PROCEDURE VALIDATE_ORDIM;
drop package body HTMLDB_SYSTEM;
drop view ALL_XML_SCHEMAS;
drop view ALL_XML_SCHEMAS2;

SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

9. Remove Oracle Text:
@?/ctx/admin/catnoctx.sql
drop procedure sys.validate_context;

select comp_id, comp_name, version, status from dba_registry where COMP_ID=’CONTEXT';
SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

10. Remove OLAP Analytic Workspace:
shutdown immediate;
startup

@?/olap/admin/catnoaps.sql
@?/rdbms/admin/utlrp.sql

select comp_id, comp_name, version, status from dba_registry where COMP_ID=’APS';
SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

11. Remove Oracle OLAP API:
@?/olap/admin/olapidrp.plb
@?/olap/admin/catnoxoq.sql
@?/rdbms/admin/utlrp.sql

select comp_id, comp_name, version, status from dba_registry where COMP_ID=’XOQ';
SELECT object_name FROM dba_objects WHERE status = ‘INVALID';

12. Remove OLAP Catalog:
shutdown immediate;
startup
@?/olap/admin/catnoamd.sql

SELECT object_name FROM dba_objects WHERE status = ‘INVALID';
select comp_id, comp_name, version, status from dba_registry where COMP_ID=’AMD';

13. Remove Java Support from an Oracle Database:
shutdown immediate;
startup
exit

alter system set “_system_trig_enabled” = false scope=memory;
alter system enable restricted session;

@?/rdbms/admin/catnojav.sql
@?/xdk/admin/rmxml.sql
@?/javavm/install/rmjvm.sql

drop table sys.JAVA$RMJVM$AUX3;
drop table sys.JAVA$RMJVM$AUX2;
drop table sys.JAVA$RMJVM$AUX;

shutdown immediate;
startup

Cleanup:
@?/rdbms/admin/catdph.sql
@?/rdbms/admin/prvtcxml.plb
@?/rdbms/admin/catdpb.sql
@?/rdbms/admin/dbmspump.sql
@?/rdbms/admin/utlrp

James Little, a London-based engineer, recently wrote about using WebSockets with kdb+.

He built a handler sending the same data to multiple clients simultaneously, or “sequentially-but-as-fast-as-possible…”
Check it out and pass along your comments directly to James on his blog.

Hi All,

Oracle Just certified JRE 1.8.0_31 with all major EBS Releases 11i, 12.0, 12.1 and 12.2

for more info :

For EBS 11i:

• Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 11i (Note 290807.1)
• Upgrading Developer 6i with Oracle E-Business Suite 11i (Note 125767.1)

For EBS 12.0, 12.1, 12.2

• Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12 (Note 393931.1)
• Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12 (Note 437878.1)