Feed aggregator

audsid

Tom Kyte - Fri, 2017-10-20 14:26
I am trying to track down the source (ie. machine and program) of a SQL that is erroring out with an ORA-00600. When the session produces a trace file, it identifies the session using the SID, serial# combination : *** SESSION ID:(1346.55751) 2017-10...
Categories: DBA Blogs

error ORA-01422 in select query

Tom Kyte - Fri, 2017-10-20 14:26
Hi, I am facing "ORA-01422: exact fetch returns more than requested number of rows" in my plsql procedure. Here are the details of test I am trying: create table cust_bug_metadata(product_id number, component varchar2(50),sub_component varchar...
Categories: DBA Blogs

PostgreSQL Index Suggestion With Powa

Yann Neuhaus - Fri, 2017-10-20 09:21

A few time ago my colleague Daniel did a blog about POWA. In a nice article he shown how this tool can be used to monitor our PostgreSQL.
In this present article I am going to show how this powerful tool can help by suggesting indexes which can optimize our queries.
I am using postgeSQL 9.6

[root@pgservertools extension]# yum install postgresql96-server.x86_64
[root@pgservertools extension]# yum install postgresql96-contrib.x86_64

And Then I initialize a cluster

[root@pgservertools extension]# /usr/pgsql-9.6/bin/postgresql96-setup initdb
Initializing database ... OK

POWA require following extensions:
pg_qualstats: gathers statistics on predicates found in WHERE statements and JOIN clauses
pg_stat_kcache : gathers statistics about real reads and writes done by the filesystem layer
hypopg : extension adding hypothetical indexes in PostgreSQL. This extension can be used to see if PostgreSQL will use the index or no
btree_gist : provides GiST index operator classes that implement B-tree equivalent behavior for various data types
powa_web : will provide access to powa via a navigator

Just we will note that following packages are installed to resolve some dependencies during the installation of these extensions.

yum install python-backports-ssl_match_hostname.noarch
rpm -ivh python-tornado-2.2.1-8.el7.noarch.rpm
rpm -ivh python-tornado-2.2.1-8.el7.noarch.rpm

And then extensions are installed using yum

yum install powa_96.x86_64 pg_qualstats96.x86_64 pg_stat_kcache96.x86_64 hypopg_96.x86_64 powa_96-web.x86_64

After the installation the postgresql.conf is modified to load the extensions

[root@pgservertools data]# grep shared_preload_libraries postgresql.conf | grep -v ^#
shared_preload_libraries = 'pg_stat_statements,powa,pg_stat_kcache,pg_qualstats' # (change requires restart)
[root@pgservertools data]#

And then restart the PostgreSQL

[root@pgservertools data]# systemctl restart postgresql-9.6.service

For POWA configuration, the first step is to create a user for powa

postgres=# CREATE ROLE powa SUPERUSER LOGIN PASSWORD 'root';
CREATE ROLE

and the repository database we will use.

postgres=# create database powa;
CREATE DATABASE

The extensions must be created in the repository database and in all databases we want to monitor

postgres=#\c powa
powa=# CREATE EXTENSION pg_stat_statements;
CREATE EXTENSION
powa=# CREATE EXTENSION btree_gist;
CREATE EXTENSION
powa=# CREATE EXTENSION powa;
CREATE EXTENSION
powa=# CREATE EXTENSION pg_qualstats;
CREATE EXTENSION
powa=# CREATE EXTENSION pg_stat_kcache;
CREATE EXTENSION
powa=# CREATE EXTENSION hypopg;
CREATE EXTENSION

We can verify that extensions are loaded in the database using

powa=# \dx
List of installed extensions
Name | Version | Schema | Description
--------------------+---------+------------+-----------------------------------------------------------
btree_gist | 1.2 | public | support for indexing common datatypes in GiST
hypopg | 1.1.0 | public | Hypothetical indexes for PostgreSQL
pg_qualstats | 1.0.2 | public | An extension collecting statistics about quals
pg_stat_kcache | 2.0.3 | public | Kernel statistics gathering
pg_stat_statements | 1.4 | public | track execution statistics of all SQL statements executed
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
powa | 3.1.1 | public | PostgreSQL Workload Analyser-core
(7 rows)
powa=#

Now let’s create a database named mydb for our tests and let’s create all extensions inside the database.

[postgres@pgservertools ~]$ psql
psql (9.6.5)
Type "help" for help.
postgres=# create database mydb;
CREATE DATABASE
postgres=#

Let’s again verify extensions into the database mydb

mydb=# \dx
List of installed extensions
Name | Version | Schema | Description
--------------------+---------+------------+-----------------------------------------------------------
btree_gist | 1.2 | public | support for indexing common datatypes in GiST
hypopg | 1.1.0 | public | Hypothetical indexes for PostgreSQL
pg_qualstats | 1.0.2 | public | An extension collecting statistics about quals
pg_stat_kcache | 2.0.3 | public | Kernel statistics gathering
pg_stat_statements | 1.4 | public | track execution statistics of all SQL statements executed
plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
powa | 3.1.1 | public | PostgreSQL Workload Analyser-core
(7 rows)
mydb=#

In mydb database we create a table mytab and insert in it some rows

mydb=# \d mytab
Table "public.mytab"
Column | Type | Modifiers
--------+---------+-----------
id | integer |
val | text |
.
mydb=# select count(*) from mytab;
count
-----------
100000000
(1 row)

The last step is to configure the powa-web configuration file. Below is our file

[root@pgservertools etc]# pwd
/etc
[root@pgservertools etc]# cat powa-web.conf
servers={
'main': {
'host': 'localhost',
'port': '5432',
'database': 'powa',
'query': {'client_encoding': 'utf8'}
}
}
cookie_secret="secret"
[root@pgservertools etc]#

And then powa-beb can be started by following command

[root@pgservertools etc]# powa-web &
[1] 5600
[root@pgservertools etc]# [I 171006 13:54:42 powa-web:12] Starting powa-web on http://0.0.0.0:8888

We can now log with the user powa we created at http://localhost:8888/
powa1

And then we can choose mydb database to monitor it
powa2

Now let’s run some queries. As my load is very low I set my pg_qualstats.sample_rate=1 in the postgresql.conf file (thanks to Julien Rouhaud)

[postgres@pgservertools data]$ grep pg_qualstats.sample_rate postgresql.conf
pg_qualstats.sample_rate = 1


mydb=# select * from mytab where id in (75,25,2014,589);
id | val
------+-----------
25 | line 25
75 | line 75
589 | line 589
2014 | line 2014
(4 rows)

Time: 9472.525 ms
mydb=#

Using the tab Index suggestions, we click on Optimize the database. We can see that an index creation is recommended with the potential gain.
powa3
powa4
powa5
We will just note that PostgreSQL uses the extension hypopg to see if the index will be used or no. Let’s see how this extension works. Hypothetical indexes are useful to know if specific indexes can increase performance of a query. They do not cost CPU as they don’t exist.
Let’s create a virtual index in mydb database

mydb=# select * from hypopg_create_index('create index on mytab (id)');
indexrelid | indexname
------------+-----------------------
55799 | btree_mytab_id
(1 row)
mydb=#

We can verify the existence of the virtual index by

mydb=# SELECT * FROM hypopg_list_indexes();
indexrelid | indexname | nspname | relname | amname
------------+-----------------------+---------+---------+--------
55799 | btree_mytab_id | public | mytab | btree
(1 row)

Using explain, we can see that PostgreSQL will use the index.

mydb=# explain select * from mytab where id in (75,25,2014,589);
QUERY PLAN
-------------------------------------------------------------------------------------
Index Scan using btree_mytab_id on mytab (cost=0.07..20.34 rows=4 width=17)
Index Cond: (id = ANY ('{75,25,2014,589}'::integer[]))
(2 rows)

Just not that explain analyze will not use the virtual index
Conclusion
In this article we see how POWA can help for optimizing our PostgreSQL database.

References: https://pgxn.org/dist/hypopg/; http://powa.readthedocs.io/en/latest/

 

Cet article PostgreSQL Index Suggestion With Powa est apparu en premier sur Blog dbi services.

Extendable Lookups vs Lookups

Anthony Shorten - Thu, 2017-10-19 20:32

The Oracle Utilities Application Framework avoids hardcoding of values for maintenance, multi-lingual and configuration purposes. One of the features that supports this requirement is the Lookup object which lists the valid values (and associated related values like the description/override description and java code name for SDK use) for the field. Lookups can be exclusively owned by the product (where you can only change the override description and not add any additional values) or can customized where you can add new values. You are also free to use F1-GetLookupDescription to get the value for a lookup in any query zone, business service, business object (though you can do this on the element definition directly) and script.

There is a maintenance function to maintain Lookups. For example:

Example Lookup

The Lookup object is ideal for simple fields with valid values but if you needed to add additional elements to the lookup the lookup object cannot be extended. The concept of an Extendable Lookup was introduced. It allows implementations to build complex configurations similar to a lookup and introduce extended features for their custom configuration settings. To use Extendable Lookup the following is typically done:

  • You create a Business Object based upon the F1-EXT LKUP Maintenance Object. You can define the structure you want to configure for the lookup. There are numerous examples of this in the base product that you can use to get ideas for what you might need to support. It is highly recommended to use UI Hints on the BO Schema to build your user interface for the lookup.
  • You can refer to the Extendable Lookup using the F1-GetExtLookUpVal common business service that can return up to five attributes from your Extendable Lookup (if you need more you can develop your own call to directly return the values - like calling the BO directly).

Here are some delivered examples of Extendable Lookups:

Example Extendable Lookups

Extendable Lookup is very powerful where you not only want to put valid values in a list but also configure additional settings to influence the outcomes of your custom code. It is recommended to use Extendable Lookup instead of Lookup if the requirements for the valid value configuration is beyond the requirement of Lookup in terms of elements to record.

For more information on both Lookups and Extendable Lookups, refer to the online documentation for further advice.

Allocation memory for varchar2 index

Tom Kyte - Thu, 2017-10-19 20:06
Hello! I have read much information about allocation memory for varchar2 as pl\sql variable and column of table. So now we have memory problem (assign awr report) with a big report. Can u explain please: 1) type StringTable is table of varchar2(320...
Categories: DBA Blogs

Alternative for SQLPlusW

Tom Kyte - Thu, 2017-10-19 20:06
Hi All, I've been reading a lot on the internet and am searching for a replacement for sqlplusw.exe. The problem is that I've written a lot of scripts and with sqlplusw.exe you could set a path by reading in an sqlfile. The solutions I've seen sofar...
Categories: DBA Blogs

Java Oracle ETL using CursorExpressions

Tom Kyte - Thu, 2017-10-19 20:06
Hi, I am attempting to export a large amount of data from multiple separate tables from Oracle 11 into a NoSQL database via a Java app utilising JDBI. The data is being read from the following tables: store, store2, staff and product. The final...
Categories: DBA Blogs

How to write a SQL to join with multiple tables and select results in a query from any on of the table (like in queue)

Tom Kyte - Thu, 2017-10-19 20:06
Hi , I have following tables . I am getting orders data from various sources in table test_orders. Then joining the items to various table for revenue percentage and then send the orders along with revenue information to another 3rd party tool for re...
Categories: DBA Blogs

Python sortedcontainers has me thinking

Bobby Durrett's DBA Blog - Thu, 2017-10-19 16:23

I was looking at the Python sortedcontainers package and it got me thinking. It is a long convoluted story and I am not sure that I can explain it clearly in a short blog post. I tried to explain all this to my wife in the last few minutes as we were driving up to a friend’s house last night and I’m sure it was confusing the way I explained it. But, I’m hoping that I can capture some of the ideas that I have thought about in a way that will be useful to others.

I have studied some computer science topics that do not directly relate to my work with Oracle databases and my review of the sortedcontainers implementation documentation tied together several things that I have studied and related them back to my work with Oracle performance tuning. I have not tested sortedcontainers to make sure that it does everything the web site says it does. But, I think it is the best Python package for doing balanced tree type of structures in memory. An AVL tree or B-tree keeps data ordered so you can quickly search for a range of key values and get them out in sorted order. Normal Oracle indexes are a type of B-tree but on disk with blocks cached in memory when queries access them. AVL trees are binary trees so each node points to at most 2 children. B-tree nodes can have many children. Sortedcontainers seem to work like a balanced tree with 1000 or so max children per node. I think it makes efficient used of Python’s built-in list objects. It seems to work well with caching within the CPU. I have not carefully reviewed the theory and tested all this out to prove that it is right but it seems likely that it is. I think it seems convincing because it ties back to other computer science topics that I have studied and to my experience with Oracle performance tuning.

I have been slowly working through an algorithms class on MIT’s OCW website. I am on a section about AVL trees. So, I was looking around at AVL trees in Python. I noticed that Rosetta Code had an AVL tree topic but no Python example until I added one. I also looked around on PyPI for an AVL tree Python package. Based on my search, I thought that bintrees was the most mature, but its web page has a note saying “Use sortedcontainers instead”. So, that made me think that sortedcontainers was the best balanced tree option in Python. The algorithms class talks about how to prove that you can work with AVL trees in O(log n) time. The sortedcontainers performance documentation has a complex explanation of its big O complexity. Also, I think that my class will discuss some of the concepts used in the sortedcontainers analysis in future lessons. So, that motivates me to go forward.

The assembly language book that I worked through helped me understand how to write programs that run faster because they make better use of the x86-64 processor’s cache and registers. Its creator seems to have designed sortedcontainers with CPU caches in mind. Right or wrong, in my mind this ties back to memory caches that affect Oracle database performance. How much of Oracle tuning relates back to how systems cache database blocks in RAM and where? You have the database block cache of course. You also have operating system filesystem cache which you might bypass with direct I/O. You may have high-speed memory cache within your SAN’s storage server. I don’t know about today but in the past disk controller cards and even disk drives themselves had memory caches. You might say, joking, that “cache is king” in database performance. At least, you have to say it is important to understand when and where database systems cache disk blocks in memory to understand why you are getting the performance you are seeing.

So, I guess my mind connected sortedcontainers with my algorithms class and assembly language book. I also connected sortedcontainers back to Oracle performance tuning. It makes me feel that digging into some computer science training is not a waste of time. It helps me to step back from Oracle database specific study and get a little theory. Also, my database work is focusing more and more on the x86-64 architecture and the Linux platform so looking at computer science on the same platform that I use for work has clear benefits.

So, I’m concerned that I have not made this post helpful to people who read it. Is it just about my experience or does it have a point for other people? Maybe the point is that it can’t hurt for an Oracle DBA to learn some computer science. Maybe you are like me and studied C.S. in school many years ago. Maybe you have learned Oracle on the job and don’t have a C.S. background. Maybe the message for both of us from my story about sortedcontainers and my “Aha!” moment is that there are benefits to studying a little computer science even if it does not directly relate to your job. There is only so much time in an Oracle DBA’s day and you can’t learn everything, but maybe it is worth putting some time into learning some C.S. theory if you can.

Bobby

Categories: DBA Blogs

Oracle Critical Patch Update October 2017 Oracle E-Business Suite Analysis and Impact

As with almost all previous Oracle E-Business Suite Critical Patch Updates (CPU), the October 2017 quarterly patch is significant and high-risk. 47 of the past 52 quarterly patches are significant and high-risk as they fix one or more SQL injection vulnerabilities or other damaging security vulnerabilities in the web application of Oracle E-Business Suite. Despite the publicity, marketing, or naming of specific vulnerabilities, this quarter is no different than previous quarters in terms of risk and prioritization within your organization.

For this quarter, there are 3 SQL injection vulnerabilities, 16 cross-site scripting (XSS) vulnerabilities, 3 information disclosures, and 4 other types of vulnerabilities fixed.  Most important is that 25 of the 26 vulnerabilities are remotely exploitable without authentication.

Externally facing Oracle E-Business Suite environments (DMZ) running iStore or iSupport should take immediate action to mitigate the two vulnerabilities impacting iStore and four vulnerabilities impacting iSupport (and Knowledge Management).  These web pages are allowed by the URL Firewall if the iStore or iSupport modules are enabled.  All six are cross-site scripting (XSS) vulnerabilities, which requires interaction with the end-user such as clicking a link but allows for the attacker to hijack the end-users session.

October 2017 Recommendations

As with almost all Critical Patch Updates, the security vulnerabilities fixes are significant and high-risk.  Corrective action should be taken immediately for all Oracle E-Business Suite environments. The most at risk implementations are those running Internet facing self-service modules (i.e., iStore, iSupplier, iSupport, etc.) and Integrigy rates this CPU as a critical risk due to the number of SQL injection vulnerabilities that can be remotely exploited without authentication.   These implementations should (1) apply the CPU as soon as possible or use a virtual patching solution such as AppDefend and (2) ensure the DMZ is properly configured according to the EBS specific instructions and the EBS URL Firewall is enabled and optimized.

Most Oracle E-Business Suite environments do not apply the CPU security patch in a timely manner and are vulnerable to full compromise of the application through exploitation of multiple vulnerabilities. If the CPU cannot be applied quickly, the only effective alternative is the use of Integrigy's AppDefend, an application firewall for the Oracle E-Business Suite.  AppDefend provides virtual patching and can effectively replace patching of EBS web security vulnerabilities.

Oracle E-Business Suite 11i

As of April 2016, the 11i CPU patches are only available for Oracle customers with Tier 1 Support. Integrigy’s analysis of the October 2017 CPU shows at least 18 of the 26 vulnerabilities are also exploitable in 11i.  11i environments without Tier 1 Support should implement a web application firewall and virtual patching for Oracle E-Business in order to remediate large number of unpatched security vulnerabilities.  As of October 2017, an unsupported Oracle E-Business Suite 11i environment will have approximately 170 unpatched vulnerabilities – a number of which are high-risk SQL injection security bugs.

11i Tier 1 Support has been extended through December 2018, thus October 2018 will be the final CPU for Oracle E-Business Suite 11i.

Oracle E-Business Suite 12.0

CPU support for Oracle E-Business Suite 12.0 ended January 2015 and there are no security fixes for this release.  Integrigy’s analysis of the CPU shows at least 22 of the 26 vulnerabilities are exploitable in 12.0. In order to protect your application environment, the Integrigy AppDefend application firewall for Oracle E-Business Suite provides virtual patching for all these exploitable web security vulnerabilities.

Oracle Critical Patch Updates
Categories: APPS Blogs, Security Blogs

Oracle SOA Suite 12c: Running BPEL processes with Jdevelopers built in weblogic server

Dietrich Schroff - Thu, 2017-10-19 14:00
After creating a BPEL process with jdeveloper i want to run this process inside the jdeveloper built in weblogic server.

Therefor you have to choose "run->start server instance (integratedweblogicserver)":


Enter a password of your choice (more than 8 characters required):

Via bash you can see the weblogic process:
$ ps auxwww|grep weblogic
schroff  17464  287  9.6 4381716 778820 pts/17 Sl+  20:54   1:11 /home/data/opt/jdk1.8.0_131/bin/java -DORACLE_HOME=/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common -Xms32m -Xmx1024m -XX:MaxPermSize=768m weblogic.WLST /home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/o.j2ee.adrs/BuildDefaultDomain2.py
The log window in jdevelopers shows up the following lines:

 [Waiting for the domain to finish building...]
[08:53:44 PM] Creating IntegratedWebLogicServer Domain...
[08:54:43 PM] Extending IntegratedWebLogicServer Domain...
[08:55:17 PM] Extending IntegratedWebLogicServer Domain...
[08:55:50 PM] Extending IntegratedWebLogicServer Domain...
[08:56:15 PM] IntegratedWebLogicServer Domain processing completed successfully.
*** Using HTTP port 7101 ***
*** Using SSL port 7102 ***
/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/bin/startWebLogic.sh
[Starting IntegratedWebLogicServer.]
[waiting for the server to complete its initialization...]
*****************************************************
** Setting up SOA specific environment...
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=512m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was removed in 8.0
*****************************************************
EXTRA_JAVA_PROPERTIES= -da:org.apache.xmlbeans...
.
LD_LIBRARY_PATH=:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/native/linux/x86_64:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/native/linux/x86_64/oci920_8
.
.
*****************************************************
** End SOA specific environment setup
*****************************************************
.
.
JAVA Memory arguments: -Xms1024m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=1024m
.
CLASSPATH=/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/user-patch.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/soa-startup.jar:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/features/com.oracle.db.jdbc7-dms.jar:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/odsi_xquery2004_12.1.3/odsi.xquery.modules_12.1.3.0.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/../oracle_common/modules/com.oracle.webservices.wls.wls-jaxrpc.jar:/home/data/opt/jdk1.8.0_131/lib/tools.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/lib/weblogic.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/../oracle_common/modules/net.sf.antcontrib_1.1.0.0_1-0b3/lib/ant-contrib.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/modules/features/oracle.wls.common.nodemanager.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.common.adapters_11.1.1/oracle.soa.common.adapters.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.cloud.adapter_12.1.3/oracle.cloud.adapter.jar:/home/data/opt/oracle/Middleware/Oracle_Home/osb/lib/servicebus-common.jar:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/communications/modules/config.jar:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/communications/modules/userprefs-config.jar:/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/soa-infra:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/quartz-all-1.6.5.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.fabric_11.1.1/oracle.soa.fabric.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.fabric_11.1.1/fabric-runtime-ext-wls.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.adapter_11.1.1/oracle.soa.adapter.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.b2b_11.1.1/oracle.soa.b2b.jar:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/internal/features/jrf_wlsFmw_oracle.jrf.wls.classpath.jar:/home/data/opt/oracle/Middleware/Oracle_Home/osb/lib/version.jar:/home/data/opt/oracle/Middleware/Oracle_Home/osb/lib/servicebus.jar:/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/osb:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.fabric_11.1.1/tracking-api.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/commons-cli-1.1.jar:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/../oracle_common/modules/com.oracle.cie.config-wls-online_8.2.0.0.jar::/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/common/derby/lib/derbynet.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/common/derby/lib/derbyclient.jar:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/common/derby/lib/derby.jar
.
PATH=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/bin:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/bin:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/../oracle_common/modules/org.apache.ant_1.9.2/bin:/home/data/opt/jdk1.8.0_131/jre/bin:/home/data/opt/jdk1.8.0_131/bin:/home/data/opt/jdk-9/bin:/home/schroff/bin:/home/schroff/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
.
***************************************************
*  To start WebLogic Server, use a username and   *
*  password assigned to an admin-level user.  For *
*  server administration, use the WebLogic Server *
*  console at http://hostname:port/console        *
***************************************************
Starting WLS with line:
/home/data/opt/jdk1.8.0_131/bin/java -server   -Xms1024m -Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=DefaultServer -Djava.security.policy=/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/lib/weblogic.policy -Djavax.net.ssl.trustStore=/tmp/trustStore3765816662939315983.jks -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true  -Xverify:none -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader -Djava.protocol.handler.pkgs=oracle.mds.net.protocol|com.bea.wli.sb.resources.url|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol -Dopss.version=12.2.1 -Digf.arisidbeans.carmlloc=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/fmwconfig/carml -Digf.arisidstack.home=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/servers/DefaultServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.ossoiap,/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.oamprovider,/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.jps -Doracle.mds.filestore.preferred=true -Dadf.version=12.2.1 -Dweblogic.jdbc.remoteEnabled=true -Dcommon.components.home=/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common -Djrf.version=12.2.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain -Doracle.server.config.dir=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/fmwconfig/servers/DefaultServer -Doracle.domain.config.dir=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/config/fmwconfig -Doracle.osb.home=/home/data/opt/oracle/Middleware/Oracle_Home/osb  -javaagent:/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/lib/debugpatch-agent.jar -da -Dwls.home=/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server -Dweblogic.home=/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server  -Djps.app.credential.overwrite.allowed=true -Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder  -da:org.apache.xmlbeans... -Dem.oracle.home=/home/data/opt/oracle/Middleware/Oracle_Home/em -DINSTANCE_HOME=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain -Djava.awt.headless=true -Doracle.sysman.util.logging.mode=dual_mode -Dsoa.archives.dir=/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa -Dsoa.oracle.home=/home/data/opt/oracle/Middleware/Oracle_Home/soa -Dsoa.instance.home=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=/home/data/opt/oracle/Middleware/Oracle_Home/wlserver/server/lib/DemoTrust.jks -Doracle.xml.schema/Ignore_Duplicate_Components=true -Doracle.xdkjava.compatibility.version=11.1.1 -Doracle.soa.compatibility.version=11.1.1 -Ddisable-implicit-bean-discovery=true -Dums.oracle.home=/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common   -Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager  weblogic.Server
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr="">
Okt 11, 2017 8:56:18 PM oracle.security.jps.wls.JpsBootStrapService start
INFORMATION: JPS-Bootstrap-Service gestartet.
<11 .10.2017="" 20:56="" mesz="" uhr=""> <"ResourceManagement" is not enabled in this JVM. Enable "ResourceManagement" to use the WebLogic Server "Resource Consumption Management" feature. To enable "ResourceManagement", you must specify the following JVM options in the WebLogic Server instance in which the JVM runs: -XX:+UnlockCommercialFeatures -XX:+ResourceManagement.>
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr="">
Okt 11, 2017 8:56:20 PM oracle.security.jps.wls.JpsDefaultService start
INFORMATION: JPS-Standardservice gestartet.
Okt 11, 2017 8:56:20 PM oracle.security.jps.JpsStartup start
INFORMATION: JPS-Initialisierung.
<11 .10.2017="" 20:56="" mesz="" uhr=""> Current log file=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/servers/DefaultServer/logs/DefaultServer.log
Rotation dir=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/servers/DefaultServer/logs
 is opened. All server side log events will be written to this file.>
Okt 11, 2017 8:56:21 PM oracle.security.jps.internal.idstore.util.LibOvdUtil pushLdapNamesToLibOvd
INFORMATION: Der LDAP-Name und die Typeninformationen wurden an libOvd übertragen. LDAPs: DefaultAuthenticator:idstore.ldap.provideridstore.ldap.
Okt 11, 2017 8:56:26 PM oracle.security.jps.internal.common.util.JpsCommonUtil initPolicyProvider
INFORMATION: OPSS Java Policy-Provider wird initialisiert.
Okt 11, 2017 8:56:26 PM oracle.security.jps.internal.common.util.JpsCommonUtil initPolicyProvider
INFORMATION: OPSS Java Policy-Provider wurde initialisiert.
Okt 11, 2017 8:56:26 PM oracle.security.jps.internal.common.util.JpsCommonUtil initPolicyProvider
INFORMATION: OPSS Java Policy-Provider ist als systemweites Policy-Objekt festgelegt.
Okt 11, 2017 8:56:26 PM oracle.security.jps.JpsStartup start
INFORMATION: JPS wurde gestartet.
<11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr=""> <11 .10.2017="" 20:56="" mesz="" uhr="">Okt 11, 2017 8:56:35 PM com.tangosol.coherence.component.util.logOutput.Jdk log
INFORMATION: 2017-10-11 20:56:35.825/19.921 Oracle Coherence 12.2.1.0.0 (thread=[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded operational configuration from "jar:file:/home/data/opt/oracle/Middleware/Oracle_Home/coherence/lib/coherence.jar!/tangosol-coherence.xml"
Okt 11, 2017 8:56:35 PM com.tangosol.coherence.component.util.logOutput.Jdk log
INFORMATION: 2017-10-11 20:56:35.878/19.974 Oracle Coherence 12.2.1.0.0 (thread=[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded operational overrides from "jar:file:/home/data/opt/oracle/Middleware/Oracle_Home/coherence/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
Okt 11, 2017 8:56:35 PM com.tangosol.coherence.component.util.logOutput.Jdk log
INFORMATION: 2017-10-11 20:56:35.973/20.069 Oracle Coherence GE 12.2.1.0.0 (thread=[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Loaded FMW commons version: 12.2.1-0-0-SNAPSHOT b60603
Okt 11, 2017 8:56:37 PM org.hibernate.validator.internal.util.Version
INFO: HV000001: Hibernate Validator 5.1.3.Final
Okt 11, 2017 8:56:37 PM oracle.dms.servlet.DMSServletFilter setEagerlySetContextValues
INFORMATION: Die Einstellung, die das vorzeitige Abrufen einiger Ausführungskontextdaten steuert, wurde auf true gesetzt.
Okt 11, 2017 8:56:37 PM oracle.ods.virtualization.engine.util.VDELogger info
INFORMATION: Notification sent for Mapping config object reloaded
<11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr="">SOA Debugger horcht auf Port 7453.

[yag][derby]:: selectQuerySELECT CONTAINER_ID, RENEWAL_TIME FROM OSB_RES_CONTAINERID_LEASE WHERE { fn timestampdiff(SQL_TSI_SECOND,RENEWAL_TIME, CURRENT_TIMESTAMP)} <#timeout_duration
<11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr="">
<11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:56="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr=""><11 .10.2017="" 20:57="" mesz="" uhr="">soa.mds.consolidation is set to false Not fusion apps envFA MDS Consolidation is NOT enabledNot fusion apps env[EL Warning]: 2017-10-11 20:58:02.613--ServerSession(1407745511)--You have specified multiple ids for the entity class [oracle.soa.tracking.fabric.persistence.jpa.QuiescedServiceHistoryDao] without specifying an @IdClass. By doing this you may lose the ability to find by identity, distributed cache support etc. Note: You may however use EntityManager find operations by passing a list of primary key fields. Else, you will have to use JPQL queries to read your entities. For other id options see @PrimaryKey.[EL Info]: 2017-10-11 20:58:03.12--ServerSession(301439769)--EclipseLink, version: Eclipse Persistence Services - 2.6.1.v20150916-55dc7c3[EL Info]: 2017-10-11 20:58:03.12--ServerSession(301439769)--Server: 12.2.1.0.0[EL Info]: connection: 2017-10-11 20:58:03.127--ServerSession(301439769)--tracking_session login successful[EL Info]: 2017-10-11 20:58:03.248--ServerSession(2117626378)--EclipseLink, version: Eclipse Persistence Services - 2.6.1.v20150916-55dc7c3[EL Info]: 2017-10-11 20:58:03.248--ServerSession(2117626378)--Server: 12.2.1.0.0[EL Info]: connection: 2017-10-11 20:58:03.253--ServerSession(2117626378)--deferred_session login successful[EL Warning]: 2017-10-11 20:58:05.916--ServerSession(2057154711)--You have specified multiple ids for the entity class [oracle.soa.tracking.fabric.persistence.jpa.QuiescedServiceHistoryDao] without specifying an @IdClass. By doing this you may lose the ability to find by identity, distributed cache support etc. Note: You may however use EntityManager find operations by passing a list of primary key fields. Else, you will have to use JPQL queries to read your entities. For other id options see @PrimaryKey.[EL Warning]: 2017-10-11 20:58:06.061--ServerSession(2107018368)--You have specified multiple ids for the entity class [oracle.soa.tracking.fabric.persistence.jpa.QuiescedServiceHistoryDao] without specifying an @IdClass. By doing this you may lose the ability to find by identity, distributed cache support etc. Note: You may however use EntityManager find operations by passing a list of primary key fields. Else, you will have to use JPQL queries to read your entities. For other id options see @PrimaryKey.#### On FabricKernelInitializerServlet, DiagnosticsFramework loaded from file:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.dms/dms.jar#### On MBeanManager, DiagnosticsFramework loaded from file:/home/data/opt/oracle/Middleware/Oracle_Home/oracle_common/modules/oracle.dms/dms.jar <> Generic SOA Debugger horcht auf Port 5004.Loading integration file at /home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/sysman/config/, emomsintg.xmlintg.xml file does not exist at emomsintg.xmlIn ConfigManager.loadProperties. propFile=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/sysman/config/emoms.propertiesRunning inside containerGetting props from mbeanTry to query mbean name for emoms.props:type=Properties,name=emoms.properties,*Try to get the Properties Attribute Map from the ConfigMBean  emoms.props:name=emoms.properties,type=Properties,Application=emGot the Proprties Attribute Map from the ConfigMBean  emoms.props:name=emoms.properties,type=Properties,Application=emThe size of the property map is 12In ConfigManager.loadProperties. propFile=/home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/sysman/config/emoms.propertiesRunning inside containerGetting props from mbeanTry to query mbean name for emoms.props:type=Properties,name=emoms.properties,*Try to get the Properties Attribute Map from the ConfigMBean  emoms.props:name=emoms.properties,type=Properties,Application=emGot the Proprties Attribute Map from the ConfigMBean  emoms.props:name=emoms.properties,type=Properties,Application=emThe size of the property map is 12Loading integration file at /home/schroff/.jdeveloper/system12.2.1.0.42.151011.0031/DefaultDomain/sysman/config/, emomsintg.xmlintg.xml file does not exist at emomsintg.xmlsecurePort = -1 isOMSSecure = 0 isOMSSecureLocked = 0:Enter.In ConfigManager.loadProperties. propFile=emomslogging.propertiesRunning inside containerGetting props from mbeanTry to query mbean name for emomslogging.props:type=Properties,name=emomslogging.properties,*Try to get the Properties Attribute Map from the ConfigMBean  emomslogging.props:name=emomslogging.properties,type=Properties,Application=emGot the Proprties Attribute Map from the ConfigMBean  emomslogging.props:name=emomslogging.properties,type=Properties,Application=emThe size of the property map is 17No logging has been configured and default agent logging support is unavailable.PAF Integration init BEGINPAF Integration init ENDProvCommonIntegration.init, registering the Page Handlers and Page Segment Handlersinside MultiOMSIntegrationFMWProv: Integration Class called and was reloaded for mePostInstallConfigIntegration:oracle_ias_farm target auth registration is done.CompositesProvIntegration init...getAllPluginOracleHomes: ConnectionService is nullgetAllPluginOracleHomes: ConnectionService is nullAnonymous url config processing:/WEB-INF/config/anonymous-access-emcore.configAnonymous-urls:[/em/IEsvgdetect.js.*, /em/LoginStatusServlet.*, /em/adf/.*, /em/adflib/.*, /em/afr/.*, /em/bi/.*, /em/bmp/discovertargets, /em/cabo/.*, /em/console/help.*, /em/console/logon/.*, /em/consoleStatus.jsp, /em/dynamicImage.*, /em/ecm/csa/CSA.jar, /em/ecm/csa/CSA.mb, /em/ecm/csa/csabanner.gif, /em/emcli/custAttrib.*, /em/emr/.*, /em/faces/logon/.*, /em/faces/helppages/.*, /em/flashbridge.*, /em/formsapp/lib/formsRecorder.jar, /em/images/.*, /em/install/getAgentImage, /em/helppages/help.*, /em/jsLibs/.*, /em/jsLibsObf/.*, /em/login.jsp, /em/mapproxy.*, /em/mobile/core/uifwk/skins/.*, /em/ocamm/lib.*, /em/onetime.*, /em/ovs/discovertargets, /em/public/.*, /em/public_lib_download/.*, /em/redirect.*, /em/relocatetarget.*, /em/sdkImpl/core/uifwkmobile/skins/*, /em/servlet/GaugeServlet.*, /em/servlet/GraphServlet.*, /em/swlib/getfile, /em/VncViewer.jar, /em/websvcs.*, /em/jobrecv.*] Found 0 composites to be loaded --------->deploying 0 composites took 1 ms [EL Info]: 2017-10-11 20:58:28.127--ServerSession(2057154711)--EclipseLink, version: Eclipse Persistence Services - 2.6.1.v20150916-55dc7c3[EL Info]: 2017-10-11 20:58:28.155--ServerSession(2057154711)--Server: 12.2.1.0.0[EL Info]: 2017-10-11 20:58:28.186--ServerSession(2057154711)--/file:/home/data/opt/oracle/Middleware/Oracle_Home/soa/soa/modules/oracle.soa.fabric_11.1.1/tracking-fabric.jar_soa_local_resiliency_persistence_unit login successfulSOA Platform is running and accepting requests. Start up took 20395 msIntegratedWebLogicServer startup time: 134139 ms.[IntegratedWebLogicServer started.]And after waiting for 134 seconds i was able to login into http://localhost:7101/console





The Oracle Fusion Middleware Control 12c can be found at http://localhost:7101/em



The deployment of the BPEL is started via "Build->Deploy->"

 Then walk though the deployment wizard:
 Deployment wizard 2/5
 Deployment wizard 3/5
 Deployment wizard 4/5
 Deployment wizard 5/5

Jdevelopers log windows should show something like:
[09:15:48 PM] ----  Deployment started.  ----
[09:15:48 PM] Target platform is  (Weblogic 12.x).
[09:15:48 PM] Running dependency analysis...
[09:15:48 PM] Building...
[09:15:52 PM] Deploying profile...
[09:15:52 PM] Wrote Archive Module to /home/schroff/jdeveloper/mywork/101.SOA/BPELHelloWorld/deploy/sca_BPELHelloWorld.jar
[09:15:52 PM] Deploying sca_BPELHelloWorld.jar to partition "default" on server DefaultServer [http://zerberus.fritz.box:7101]
[09:15:52 PM] Processing sar=/home/schroff/jdeveloper/mywork/101.SOA/BPELHelloWorld/deploy/sca_BPELHelloWorld.jar
[09:15:52 PM] Adding sar file - /home/schroff/jdeveloper/mywork/101.SOA/BPELHelloWorld/deploy/sca_BPELHelloWorld.jar
[09:15:52 PM] Preparing to send HTTP request for deployment
[09:15:52 PM] Creating HTTP connection to host:zerberus.fritz.box, port:7101
[09:15:52 PM] Sending internal deployment descriptor
[09:15:52 PM] Sending archive - sca_BPELHelloWorld.jar
[09:15:54 PM] Received HTTP response from the server, response code=200
[09:15:54 PM] Successfully deployed archive sca_BPELHelloWorld.jar with 0 warning/severe messages to partition "default" on server DefaultServer [http://zerberus.fritz.box:7101]
[09:15:54 PM] Elapsed time for deployment:  7 seconds
[09:15:54 PM] ----  Deployment finished.  ----
Inside the Fusion Middleware Control EM (http://localhost:7101/em) you can find the BPEL here (you have to click on this grey folder icon):


 Then click on "Testen" (i guess "Test" in other localizations) and you will get this site, where you can add the input string:
And after running the test you will get:

The button "start flow trace" will take you to the audit trails:







Question Time

Jonathan Lewis - Thu, 2017-10-19 13:15

It’s that time of year again – the UKOUG Tech conference is approaching and I’ve organised a panel session on the Cost Based Optimizer.

This year I’ve got Christian Antognini, Nigel Bayliss, Maria Colgan and special guest star, all the way from Australia, Richard Foote on the panel, with Neil Chandler and Martin Widlake taking on their inimitable role of MCs.

If you’ve got any questions you’d like to put to the panel, you will have a chance to write them down on the day, but it would be nice to have a few supplied in advance in the comment below.  Tactical, strategic, technical, or just plain curious – this is a panel that can tell you what can be done, what shouldn’t be done, and how to do the things you shouldn’t do but sometimes have to.

If you prefer to email your questions then click this link.


Using Flyway to Manage Oracle DB Versions in the Cloud

Shay Shmeltzer - Thu, 2017-10-19 13:11

This is another entry in my series about managing database scripts/schema as part of agile development. In the past I showed how to use simple SQL and Liquibase to manage schema creation/population scripts, and today I'll show you how to use Flyway.

Flyway log

Flyway is a free open source solution for managing "database migrations" - or basically helping you keep multiple database in synch by tracking and applying changes to the schema structure and data.

Flyway uses simple SQL scripts - which means you can use DB specific syntax - and tracks their execution in the database through a table it maintains. It is very easy to get started with and only has 6 commands that you need to be familiar with.

The main command is "migrate" which will check your database status, and then run all the newer scripts that have yet to be run on that instance.

Flyway uses a directory structure that contains a sql folder where you'll host all your SQL scripts. It uses a naming convention (that can be adjusted) where you start the file name with a Version number (V1, V1.1, V2.1) and then two "_" followed by a description - so something like V1__Create_Emp_Table - will show up as "Create Emp Table" when you issue the "info" command to find out what is the status of a database and which scripts have already run. By the way, the info command will also show you which new scripts are pending to be run on a specific database instance.

In the video below I show how to configure and use Flyway, and how to integrate it into an automatic DevOps process leveraging Oracle Developer Cloud Service. (including task tracking, Git version management of the source, and build execution of the scripts).

Flyway can integrate with various build framework (ant, maven, gradle etc), but since many DB folks are not familiar with those, I chose to use simple command lines in my demo to invoke Flyway. On my laptop and local MySQL DB I just used the Flyway command line utility. However Flyway is not installed by default in the DevCS servers, so I did a little trick:

Flyway is a Java program, so into my DevCS Git repository I uploaded the Flyway directory along with needed jars for flyway and the JDBC driver. Then I looked at the script for invoking the command line and found out the Java command they used and copied it into a regular shell command in my build:

java -cp lib/flyway-commandline-4.2.0.jar:lib/flyway-core-4.2.0.jar org.flywaydb.commandline.Main info -user=fw -password=$Password -url=jdbc:oracle:thin:@ipaddress:1521/servicename

The $Password refers to a build parameter which is encrypted.

The directory structure and files in my Git are shown in this image:

directory structure

 

Categories: Development

JRE 1.8.0_151/152 Certified with Oracle EBS 12.1 and 12.2

Steven Chan - Thu, 2017-10-19 11:23

Java logo

Java Runtime Environment 1.8.0_151 (a.k.a. JRE 8u151-b12) and JRE 1.8.0_152 (a.k.a. JRE 8u152-b16) and later updates on the JRE 8 codeline are now certified with Oracle E-Business Suite 12.1 and 12.2 for Windows clients.

Java Web Start is available

This JRE release may be run with either the Java plug-in or Java Web Start.

Java Web Start is certified with EBS 12.1 and 12.2 for Windows clients.  

Considerations if you're also running JRE 1.6 or 1.7

The JRE 1.7.0_161 and 1.6.0_171 updates included an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available as of those two Java releases. It is expected that Java deployment technology will not be packaged in later Java 6 or 7 updates.

JRE 1.7.0_161 and 1.6.0_171 can still run Java content.  They cannot launch Java.

End-users who only have JRE 1.7.0_161 or 1.6.0_171 -- and not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.7 or 1.6 for compatibility with other third-party Java applications must also install the October 2017 PSU release JRE 1.8.0_152 on their desktops.

Once JRE 1.8.0_152 is installed on a Windows desktop, it can be used to launch JRE 1.7.0_161 and 1.6.0_171 and later updates for their respective codelines. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

Where are the official patch requirements documented?

All patches required for ensuring full compatibility of the E-Business Suite with JRE 8 are documented in these Notes:

For EBS 12.1 & 12.2

Implications of Java 6 and 7 End of Public Updates for EBS Users

The Oracle Java SE Support Roadmap and Oracle Lifetime Support Policy for Oracle Fusion Middleware documents explain the dates and policies governing Oracle's Java Support.  The client-side Java technology (Java Runtime Environment / JRE) is now referred to as Java SE Deployment Technology in these documents.

Starting with Java 7, Extended Support is not available for Java SE Deployment Technology.  It is more important than ever for you to stay current with new JRE versions.

If you are currently running JRE 6 on your EBS desktops:

  • You can continue to do so until the end of Java SE 6 Deployment Technology Extended Support in June 2017
  • You can obtain JRE 6 updates from My Oracle Support.  See:

If you are currently running JRE 7 on your EBS desktops:

  • You can continue to do so until the end of Java SE 7 Deployment Technology Premier Support in July 2016
  • You can obtain JRE 7 updates from My Oracle Support.  See:

If you are currently running JRE 8 on your EBS desktops:

Will EBS users be forced to upgrade to JRE 8 for Windows desktop clients?

No.

This upgrade is highly recommended but remains optional while Java 6 and 7 are covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JRE 6 and 7 desktop clients. Note that there are different impacts of enabling JRE Auto-Update depending on your current JRE release installed, despite the availability of ongoing support for JRE 6 and 7 for EBS customers; see the next section below.

Impact of enabling JRE Auto-Update

Java Auto-Update is a feature that keeps desktops up-to-date with the latest Java release.  The Java Auto-Update feature connects to java.com at a scheduled time and checks to see if there is an update available.

Enabling the JRE Auto-Update feature on desktops with JRE 6 installed will have no effect.

With the release of the January Critical patch Updates, the Java Auto-Update Mechanism will automatically update JRE 7 plug-ins to JRE 8.

Enabling the JRE Auto-Update feature on desktops with JRE 8 installed will apply JRE 8 updates.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

JRE 8 is certified for Mac OS X 10.8 (Mountain Lion), 10.9 (Mavericks), 10.10 (Yosemite), and 10.11 (El Capitan) desktops.  For details, see:

Will EBS users be forced to upgrade to JDK 8 for EBS application tier servers?

No.

JRE is used for desktop clients.  JDK is used for application tier servers.

JRE 8 desktop clients can connect to EBS environments running JDK 6 or 7.

JDK 8 is not certified with the E-Business Suite.  EBS customers should continue to run EBS servers on JDK 6 or 7.

Known Issues

Internet Explorer Performance Issue

Launching JRE 1.8.0_73 through Internet Explorer will have a delay of around 20 seconds before the applet starts to load (Java Console will come up if enabled).

This issue fixed in JRE 1.8.0_74.  Internet Explorer users are recommended to uptake this version of JRE 8.

Form Focus Issue Clicking outside the frame during forms launch may cause a loss of focus when running with JRE 8 and can occur in all Oracle E-Business Suite releases. To fix this issue, apply the following patch:

References

Related Articles
Categories: APPS Blogs

JRE 1.7.0_161 Certified with Oracle E-Business Suite 12.1 and 12.2

Steven Chan - Thu, 2017-10-19 11:23

Java logo

Java Runtime Environment 1.7.0_161 (a.k.a. JRE 7u161-b13) and later updates on the JRE 7 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

What's new in this update?

This update includes an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available as of this Java release. It is expected that Java deployment technology will not be packaged in later Java 7 updates.

JRE 1.7.0_161 can still run Java content.  It cannot launch Java.

End-users who only have JRE 1.7.0_161 -- and not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.7 for compatibility with other third-party Java applications must also install the October 2017 PSU release JRE 1.8.0_152 or higher on their desktops.

Once JRE 1.8.0_152 is installed on a Windows desktop, it can be used to launch JRE 1.7.0_161 and later updates on the JRE 1.7 codeline. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Recommended Browser documentation for your EBS release for details.

Where are the official patch requirements documented?

How can EBS customers obtain Java 7?

EBS customers can download Java 7 patches from My Oracle Support.  For a complete list of all Java SE patch numbers, see:

Both JDK and JRE packages are now contained in a single combined download.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package. 

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

Java Auto-Update Mechanism

With the release of the January 2015 Critical patch Updates, the Java Auto-Update Mechanism will automatically update JRE 7 plug-ins to JRE 8.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), and 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE ("Deployment Technology") is used for desktop clients.  JDK is used for application tier servers.

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 (excluding Deployment Technology) is covered by Extended Support until December 2018.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 (excluding Deployment Technology) by December 2018. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is certified with E-Business Suite 12.  See:

Known Issues

When using Internet Explorer, JRE 1.7.0_01 had a delay of around 20 seconds before the applet started to load. This issue is fixed in JRE 1.7.0_95.

References

Related Articles
Categories: APPS Blogs

JRE 1.6.0_171 Certified with Oracle E-Business Suite 12.1 and 12.2

Steven Chan - Thu, 2017-10-19 11:23

Java logThe latest Java Runtime Environment 1.6.0_171 (a.k.a. JRE 6u171-b13) and later updates on the JRE 6 codeline are now certified with Oracle E-Business Suite Release 12.1 and 12.2 for Windows-based desktop clients.

What's new in this update?

This update includes an important change: the Java deployment technology (i.e. the JRE browser plugin) is no longer available as of this Java release. It is expected that Java deployment technology will not be packaged in later Java 6 updates.

JRE 1.6.0_171 can still run Java content.  It cannot launch Java.

End-users who only have JRE 1.6.0_171 -- and not JRE 1.8 -- installed on their Windows desktop will be unable to launch Java content.

End-users who need to launch JRE 1.6 for compatibility with other third-party Java applications must also install the October 2017 PSU release JRE 1.8.0_152 or higher on their desktops.

Once JRE 1.8.0_152 is installed on a Windows desktop, it can be used to launch JRE 1.6.0_171 and later updates on the JRE 1.6 codeline. 

How do I get help with this change?

EBS customers requiring assistance with this change to Java deployment technology can log a Service Request for assistance from the Java Support group.

All JRE 6, 7, and 8 releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops:

  • From JRE 1.6.0_03 and later updates on the JRE 6 codeline
  • From JRE 1.7.0_10 and later updates on the JRE 7 codeline 
  • From JRE 1.8.0_25 and later updates on the JRE 8 codeline
We test all new JRE releases in parallel with the JRE development process, so all new JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

You do not need to wait for a certification announcement before applying new JRE 6, 7, or 8 releases to your EBS users' desktops.

Effects of new support dates on Java upgrades for EBS environments

Support dates for the E-Business Suite and Java have changed.  Please review the sections below for more details:

  • What does this mean for Oracle E-Business Suite users?
  • Will EBS users be forced to upgrade to JRE 7 for Windows desktop clients?
  • Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?
32-bit and 64-bit versions certified

This certification includes both the 32-bit and 64-bit JRE versions for various Windows operating systems. See the respective Deploying JRE documentation for your EBS release for details.

How can EBS customers obtain Java 6 updates?

Java 6 is now available only via My Oracle Support for E-Business Suite users.  You can find links to this release, including Release Notes, documentation, and the actual Java downloads here: Both JDK and JRE packages are contained in a single combined download after 6u45.  Download the "JDK" package for both the desktop client JRE and the server-side JDK package.

Coexistence of multiple JRE releases Windows desktops

The upgrade to JRE 8 is recommended for EBS users, but some users may need to run older versions of JRE 6 or 7 on their Windows desktops for reasons unrelated to the E-Business Suite.

Most EBS configurations with IE and Firefox use non-static versioning by default. JRE 8 will be invoked instead of earlier JRE releases if both are installed on a Windows desktop. For more details, see "Appendix B: Static vs. Non-static Versioning and Set Up Options" in Notes 290807.1 and 393931.1.

What do Mac users need?

Mac users running Mac OS X 10.10 (Yosemite) can run JRE 7 or 8 plug-ins.  See:

Will EBS users be forced to upgrade to JDK 7 for EBS application tier servers?

JRE ("Deployment Technology") is used for desktop clients.  JDK is used for application tier servers.

JDK upgrades for E-Business Suite application tier servers are highly recommended but currently remain optional while Java 6 is covered by Extended Support. Updates will be delivered via My Oracle Support, where you can continue to receive critical bug fixes and security fixes as well as general maintenance for JDK 6 for application tier servers. 

Java SE 6 (excluding Deployment Technology) is covered by Extended Support until December 2018.  All EBS customers with application tier servers on Windows, Solaris, and Linux must upgrade to JDK 7 by December 2018. EBS customers running their application tier servers on other operating systems should check with their respective vendors for the support dates for those platforms.

JDK 7 is the latest Java release certified with E-Business Suite 12 servers.  See:

References

Related Articles
Categories: APPS Blogs

Managing Oracle Big Data Cloud – CE with REST API

Yann Neuhaus - Thu, 2017-10-19 10:29

In this blog post, we will see how to manage Oracle Public Cloud Big Data service Compute Edition with REST API. Scheduling the start/stop/restart of a metered PaaS in the Oracle cloud can be interesting for managing your cloud credits consumptions.

We need first consult the official documentation, to understand how the API is composed. https://docs.oracle.com/en/cloud/paas/big-data-compute-cloud/csbdp/QuickStart.html 

Use the following URL composition for accessing to REST endpoint:
https://region-prefix.oraclecloud.com/resource-path

According to Oracle documentation, the following information should be taken into account.

Connection Information:

  • Identity Domain: axxxxxx
  • REstFull URL: https://psm.europe.oraclecloud.com/
  • username -password

Terminology:

  • {instanceName} = Name of the BDCS-CE service (= Cluster Name)
  • {identityDomainId} = “X-ID-TENANT-NAME: axxxxxx”
  • {function} = start, stop, restart
  • {allServiceHosts} = the entire cluster VMs (all instances which composed the cluster)
  • “Accept: <value>” = Media Type (default value = application/json)

Before starting an automation script to manage your Big Data cluster, execute single GET/POST commands to understand how the API is working.

GET request: View all Service BDCS-CE instances

/paas/api/v1.1/instancemgmt/{identityDomainId}/services/BDCSCE/instances

curl -i -X GET \
        -u "username:password" \
        -H "X-ID-TENANT-NAME: axxxxxx" \
        -H "Accept: application/json" \
        "https://psm.europe.oraclecloud.com/paas/api/v1.1/instancemgmt/axxxxxx/services/BDCSCE/instances"

Result:

HTTP/1.1 200 OK
Server: Oracle-Application-Server-11g
Strict-Transport-Security: max-age=31536000;includeSubDomains
Content-Language: en
...

{"services":{"cluster-iot":{"...

According to the HTTP status code, the command was successful.

GET request: View a specific Service BDCS-CE instances

Add the instance name to get the status of a specific cluster. Note that a BDCS-CE instance is your Big Data cluster.

/paas/api/v1.1/instancemgmt/{identityDomainId}/services/BDCSCE/instances/{instanceName}

curl -i -X GET \
        -u "username:password" \
        -H "X-ID-TENANT-NAME: axxxxxx" \
        -H "Accept: application/json" \
        "https://psm.europe.oraclecloud.com/paas/api/v1.1/instancemgmt/axxxxxx/services/BDCSCE/instances/cluster-iot"

Then use the same requests structure to start/stop/restart your Big Data cluster.

POST request: Start / Stop / Restart Service Instances BDCS-CE: cluster-iot

/paas/api/v1.1/instancemgmt/{identityDomainId}/services/BDCSCE/instances/{instanceName}/hosts/{function}

As it’s specified in the documentation, you need to change the media type to application/vnd.com.oracle.oracloud.provisioning.Service+json and use a body parameter to specify which hosts you want to manage. In our case, we want to manage all cluster hosts.

curl -i -X POST -u "username:password" \
-H "X-ID-TENANT-NAME: axxxxxx" \
-H "Content-Type: application/vnd.com.oracle.oracloud.provisioning.Service+json" \
-d '{"allServiceHosts":"true"}' "https://psm.europe.oraclecloud.com/paas/api/v1.1/instancemgmt/axxxxxx/services/BDCSCE/instances/cluster-iot/hosts/stop"

You can now, start to develop an automation script to manage your Oracle Big Data Compute Edition cluster.

Python prerequistes:

Install Python-PIP before:

dbi@host:~/$ sudo apt-get install python-pip

Install Requests module with PIP:

dbi@host:~/$ sudo pip install requests

Code:

#!/usr/bin/env python
# -*- coding: utf-8 -*-
"""
__author__ = "Mehdi Bada"
__company__= dbi services sa
__version__ = "1.0"
__maintainer__ = "Mehdi Bada"
__email__ = ""
__status__ = "Dev"

"""

import os, sys, getopt
import requests
import simplejson
import json

# Variables defintion.

identityDomainId="axxxxxx"
instanceName="cluster-iot"
server = "https://psm.europe.oraclecloud.com"
commands = ['start', 'stop', 'restart']


def usage():
    print "\nScript Usage \n"
    print "Usage:", sys.argv[0], "-c [start|stop|restart] | -h \n"

if len(sys.argv) < 3:
    usage()
    sys.exit(2)

try:
    opts, args = getopt.getopt(sys.argv[1:], "ch", ["command", "help"])
except getopt.GetoptError:
    usage()
    sys.exit(2)

for opt, arg in opts:
    if opt in ("-h", "--help"):
        usage()
        sys.exit()
    elif opt in ("-c", "--command"):
        icommand=sys.argv[2]
        if icommand in commands:
                icommand=sys.argv[2]
        else:
                usage()
                sys.exit(2)


url = server + "/paas/api/v1.1/instancemgmt/%s/services/BDCSCE/instances/%s/hosts/%s" % (identityDomainId,instanceName,icommand)

payload = "{\"allServiceHosts\":\"true\"}"

headers = {
    'x-id-tenant-name': "%s" %(identityDomainId),
    'accept': "application/vnd.com.oracle.oracloud.provisioning.Service+json",
    'content-type': "application/json",
    'authorization': " ",
    }

response = requests.request("POST", url, data=payload, headers=headers)

# Print the status code of the response.
print("\n")
print(response.status_code)

# Json Parsing
content=response.content
j = simplejson.loads(content)
print (j['details']['message'])

Usage:

dbi@host:~/$ ./bdcsce_start_stop_test.py -h

Script Usage

Usage: ./bdcsce_start_stop_test.py -c [start|stop|restart] | -h

 

Oracle REST API is not very well documented, that why multiple tests should be performed before understanding how it works.

 

Cet article Managing Oracle Big Data Cloud – CE with REST API est apparu en premier sur Blog dbi services.

Datascape Podcast: Episode 16 – Recapping Oracle OpenWorld 2017

Pythian Group - Thu, 2017-10-19 08:26

Today we’re going to recap some of the most interesting concepts from the recently completed Oracle OpenWorld 2017 and to help us navigate this I have invited Simon Pane back to the show. Simon is an accomplished Principal Consultant, who has developed a multitude of complex solutions for Pythian clients. He leverages his understanding of the industry and technologies such as Oracle, SQL Server, Linux, Oracle Cloud, AWS and more, to propose timely solutions that best suit the needs of clients. Also joining us for the first time is Ivica Arsov. Ivica is an Oracle Certified Master 12c and 11g, and a recognized member of the Oracle ACE Program as an Oracle ACE Associate. He is a blogger and active contributor to the Oracle community and presents at many technology conferences. Known for his deep Oracle expertise and ability to troubleshoot quickly and efficiently, Ivica has the skills to solve problems quickly regardless of size and complexity. Keep listening to hear more!


Key points from this episode:

  • Simon tells us more about his career at Pythian and the work he is doing with Oracle.
  • Ivica shares with us on the work he is doing with Oracle while working at Pythian.
  • The atmosphere at OOW this year.
  • The common theme of automation and security.
  • Competitive threats versus security threats.
  • The new version of the Oracle database, 18c.
  • Improvements in reduction of danger surrounding patching by balancing risk.
  • The new autonomous feature and the NRX guarantee.
  • Elasticity and automatic scaling.
  • DBA’s focusing on tasks specific to the business in the world of automation.
  • The trade-off of simplicity versus index.
  • Machine learning being introduced with cyber security.
  • New features coming out with 18c and 19c releases and architecture versions.
  • Understanding how customers are at the mercy of vendors.
  • Certifications bundled to a number of versions.
  • Industry problems around tools and security assessment.
  • Hear more about Ivica and some of his favorites in the lightning round.
  • Simon tells us more about the UK Oracle User Group Conference taking place.
  • And much more!

Links Mentioned in Today’s Episode:

Oracle OpenWorld 2017
Simon Pane
Ivica Arsov
Pythian
Amazon 
Microsoft
Oracle
Microsoft Azure
Dataguard
Rac
The book, Transaction Processing: Concepts and Techniques
UK Oracle User Group

Categories: DBA Blogs

How to expand Exadata Database Storage capacity on demand

Syed Jaffar - Thu, 2017-10-19 04:27


Exadata Storage expansion

Most of us knew the capabilities that Exadata Database Machine delivers. Its known fact that Exadata comes in different fixed rack size capacity: 1/8 rack (2 db nodes, 3 cells), quarter rack (2 db nodes, 3 cells), half rack (4 db nodes, 7 cells) and full rack (8 db nodes, 14 cells). When you want to expand the capacity, it must be in fixed size as well, like, 1/8 to quarter, quarter to half and half to full.

With Exadata X5 Elastic configuration, one can also have customized sizing by extending capacity of the rack by adding any number of DB servers or storage servers or combination of both, up to the maximum allowed capacity in the rack.

In this blog post, I will summarize and walk through a procedure about extending Exadata storage capacity, i.e, adding a new cell to an existing Exadata Database Machine.

Preparing to Extend Exadata Database Machine

·        Ensure HW placed in the rack, and all necessary network and cabling requirements are completed. (2 IPs from the management network is required for the new cell).
·         
·        Re-image or upgrade of image:
o   Extract the imageinfo from one of the existing cell server.
o   Login to the new cell through ILOM, connect to the console as root user and get the imageinfo
o   If the image version on the new cell doesn’t match with the existing image version, either you download the exact image version and re-image the new cell or upgrade the image on the existing servers.

Review "Reimaging Exadata Cell Node Guidance (Doc ID 2151671.1)" if you want to reimage the new cell.
  • Add the IP addresses acquired for the new cell to the /etc/oracle/cell/network-config/cellip.ora file on each DB node. To do this, perform the steps below from the first 1 db serer in the cluster:
    • cd /etc/oracle/cell/network-config
    • cp cellip.ora cellip.ora.orig
    • cp cellip.ora cellip.ora-bak
 
    • Add the new entries to /etc/oracle/cell/network-config/cellip.ora-bak.
    • /usr/local/bin/dcli -g database_nodes -l root -f cellip.ora-bak -d /etc/oracle/cell/network-config/cellip.ora

  • If ASR alerting was set up on the existing storage cells, configure cell ASR alerting for the cell being added.
    • List the cell attributes required for configuring cell ASR alerting. Run the following command from any existing storage grid cell:
o   CellCLI> list cell attributes snmpsubscriber
    • Apply the same SNMP values to the new cell by running the command below as the celladmin user, as shown in the below example:
o   CellCLI> alter cell snmpSubscriber=((host='10.20.14.21',port=162,community=public))
  • Configure cell alerting for the cell being added.
    • List the cell attributes required for configuring cell alerting. Run the following command from any existing storage grid cell:
o   CellCLI> list cell attributes
o    notificationMethod,notificationPolicy,smtpToAddr,smtpFrom,
o    smtpFromAddr,smtpServer,smtpUseSSL,smtpPort
    • Apply the same values to the new cell by running the command below as the celladmin user, as shown in the example below:
o   CellCLI> alter cell notificationmethod='mail,snmp',notificationpolicy='critical,warning,clear',smtptoaddr= 'dba@email.com',smtpfrom='Exadata',smtpfromaddr='dba@email.com',smtpserver='10.20.14.21',smtpusessl=FALSE,smtpport=25
  • Create cell disks on the cell being added.
    • Log in to the cell as celladmin and run the following command:
o   CellCLI> create celldisk all
    • Check that the flash log was created by default:
o   CellCLI> list flashlog
You should see the name of the flash log. It should look like cellnodename_FLASHLOG, and its status should be "normal".
If the flash log does not exist, create it using:
CellCLI> create flashlog all
    • Check the current flash cache mode and compare it to the flash cache mode on existing cells:
o   CellCLI> list cell attributes flashcachemode
To change the flash cache mode to match the flash cache mode of existing cells, do the following:
i. If the flash cache exists and the cell is in WriteBack flash cache mode, you must first flush the flash cache:
CellCLI> alter flashcache all flush
Wait for the command to return.
ii. Drop the flash cache:
CellCLI> "drop flashcache all"
iii. Change the flash cache mode:
CellCLI> "alter cell flashCacheMode=writeback_or_writethrough"
The value of the flashCacheMode attribute is either writeback or writethrough. The value must match the flash cache mode of the other storage cells in the cluster.
iv. Create the flash cache:
cellcli -e create flashcache all
  • Create grid disks on the cell being added.
    • Query the size and cachingpolicy of the existing grid disks from an existing cell.
o   CellCLI> list griddisk attributes name,asmDiskGroupName,cachingpolicy,size,offset
    • For each disk group found by the above command, create grid disks on the new cell that is being added to the cluster. Match the size and the cachingpolicy of the existing grid disks for the disk group reported by the command above. Grid disks should be created in the order of increasing offset to ensure similar layout and performance characteristics as the existing cells. For example, the "list griddisk" command could return something like this:
o   DATAC1          default         5.6953125T         32M
o   DBFS_DG         default         33.796875G         7.1192474365234375T
o   RECOC1          none            1.42388916015625T  5.6953582763671875T
When creating grid disks, begin with DATAC1, then RECOC1, and finally DBFS_DG using the following command:
CellCLI> create griddisk ALL HARDDISK PREFIX=DATAC1, size=5.6953125T, cachingpolicy='default', comment="Cluster cluster-clux6 DR diskgroup DATAC1"

CellCLI> create griddisk ALL HARDDISK PREFIX=RECOC1,size=1.42388916015625T, cachingpolicy='none', comment="Cluster cluster-clux6 DR diskgroup RECOC1"

CellCLI> create griddisk ALL HARDDISK PREFIX=DBFS_DG,size=33.796875G, cachingpolicy='default', comment="Cluster cluster-clux6 DR diskgroup DBFS_DG"
CAUTION: Be sure to specify the EXACT size shown along with the unit (either T or G).
  • Verify the newly created grid disks are visible from the Oracle RAC nodes. Log in to each Oracle RAC node and run the following command:
·        $GI_HOME/bin/kfod op=disks disks=all | grep cellName_being_added
This should list all the grid disks created in step 7 above.
  • Add the newly created grid disks to the respective existing ASM disk groups.
·        alter diskgroup disk_group_nameadd disk 'comma_separated_disk_names';
The command above kicks off an ASM rebalance at the default power level. Monitor the progress of the rebalance by querying gv$asm_operation:
SQL> select * from gv$asm_operation;
Once the rebalance completes, the addition of the cell to the Oracle RAC is complete.
  • Download and run the latest exachk to ensure that the resulting configuration implements the latest best practices for Oracle Exadata.
References:

http://docs.oracle.com/cd/E80920_01/DBMMR/extending-exadata.htm#DBMMR21158
Reimaging Exadata Cell Node Guidance (Doc ID 2151671.1)

 







Dynamic SQL in CURSOR

Tom Kyte - Thu, 2017-10-19 01:46
Hi, I am trying to create a procedure that will display logs. It has an IN parameter which is the table nam, the cursor will SELECT data based on that parameter. I cannot compile my procedure. Hope you can help me. :) <code>CREATE OR REPLACE PROCE...
Categories: DBA Blogs

Pages

Subscribe to Oracle FAQ aggregator