Feed aggregator

The Oracle Database Appliance is shipped with a bare-metal installation which may not be the latest version. You may want to have it virtualized, or get the latest version to avoid further upgrade, or install an earlier version to be in the same configuration as another ODA already in production. The easiest for all cases is to start with a re-image as soon as the ODA is plugged. This post is not a documentation, just a quick cheat sheet.

I don’t want to spend hours in the data center, so the first step, once the ODA is racked, cabled and plugged, is to get it accessible from the management network. Then all tasks can be done from a laptop, accessing the ILOM interface through a browser (Java required, and preferably 32-bits) before the public network is setup.

Here is the back of the server where you find the management network port.

This was an X5-2 but very similar to X6-2. You can look at the 3D view of X6-2 to get a better view.
There is also VGA and USB to plug a monitor and keyboard just for the time to setup the management network.

You can also use the serial port which is just next to it but I usually don’t have a serial adapter for my laptop.

You can plug a keyboard and monitor and log on the server: root password is welcome1 (no need to change it for the moment as we will re-image the machine)

In ODA X6-HA you have two nodes, numbered 0 and 1 and called oak1 and oak2 … be careful. You may wonder which server is node 0 and which one is node 1, because the servers are the same. Yes, that’s true. The nodes are identified from the storage port they are connected to. The node 0 is the one connected to the blue mini-SAS and the red ones are for node 1.

• Blue cable – Node 0 – oak1
• Red cable – Node 0 – oak2

Here I’m on node 0 and check hardware version

[root@oak1 ~]# /opt/oracle/oak/bin/oakcli show env_hw
BM ODA X6-2

This means Bare Metal X6-2 HA, a virtualized one would show VM-ODA_BASE ODA X6-2, and ODA X6-2S would show BM ODA_Lite X6-2 Small.

From storage topology, we confirm that this node has been recognized as node 0:


[root@oak1 ~]# /opt/oracle/oak/bin/oakcli validate -c StorageTopology
It may take a while. Please wait...
INFO : ODA Topology Verification
INFO : Running on Node0
INFO : Check hardware type
SUCCESS : Type of hardware found : X5-2
INFO : Check for Environment (Bare Metal or Virtual Machine)


And finally check the version because you may be lucky to get the version you want and then don’t need to re-image (I switched to node 1 here):

Of course, you don’t need to re-image when you want an higher version. You can upgrade it, but re-image is simple.

The management network interface can get an address from DHCP. But who runs DHCP on the management network? There are two ways to assign a static IP to the management network.

You may use the IPMI Tool commands:
ipmitool -I open sunoem cli
cd SP
cd Network
ls
set pendingipadress=192.168.15.101
set pendingnetmask=255.255.255.0
set pendingipgateway=192.168.15.1
set commitpending=true
Here is an example:

Or you can go to BIOS. It goes fast but filming in slow motion shows that the key is F2:

Once you are in the BIOS interface, go to Advanced, then choose ‘BMC Network configuration’ to configure IPMI and enter the following BMC Lan information:
 
IPv4 IP Assignment [Static] IPv4 address 192.168.15.102
IPv4 Subnet Mask 255.255.255.0
IPv4 Default Gateway 192.168.15.1

Once you are in the BIOS you can choose to boot on the CD-ROM first because I sometimes have problems to set that from the ILOM Web interface.

Once you have validated that the ILOM IP address can be reached from your office, you can remove the keyboard and monitor and leave the datacenter. the hardware is ok. Now the software can be deployed from the ILOM Web interface. The password to connect to ILOM from the Web browser is ‘changeme’ and you should change it.

The latest ISO image for Bare Metal or Virtualized ODA can be found from Note 88888.1
You can also find the oldest versions:

• Bare Metal: https://updates.oracle.com/download/12999313.html
• Virtualized: https://updates.oracle.com/download/16186163.html

From the ILOM you you get to the console of node 0:

From there, you can attach the ISO image: ILOM Remote Control / Devices / CD-ROM Images

and then reboot on the CD-ROM:

Reboot (Host Control / Next Boot Device / CD-ROM )

Do that for both nodes (you can run them at the same time) and prepare the information for the deployment and download the ‘End-User RDBMS Clone files’ for the database version you want.

You can download the Oracle Appliance Manager Configurator and take your time to setup and verify the configuration.

Here is part of the information to prepare. First, you will configure the network to be able to scp the software (Grid Infrastructure and Database):

[root@oak1 ~]# /opt/oracle/oak/bin/oakcli configure firstnet
Configure the network for node(s) (local,global) [global]:
The network configuration for both nodes:
hostname: Hostname lookup failure
Domain Name: pachot.net
DNS Servers: Primary DNS Server: 8.8.8.8
Node Name Host Name
0 myserver1
1 myserver2
Choose the network interface to configure (net1,net2) [net1]:
Enter the IP address for net1 on Node 0: 192.168.16.101
Enter the IP address for net1 on Node 1: 192.168.16.102
Netmask for net1: 255.255.255.0
Gateway address for net1 [192.168.16.1]:

Note that this is a funny example. I hope you don’t use the 192.168.16/24 as you public network because this is used for the private interconnect where IP addresses 192.168.16.24 and 192.168.16.25 are hardcoded. But thanks to that the configure-network can be run fron one node only.

Now that you have access through the public network, you can copy (scp) the Oracle Home clones and the configuration file to /tmp, unpack the .zip (for i in *.zip ; do /opt/oracle/oak/bin/oakcli unpack -package $i ; done) and run deploy (ssh -X /opt/oracle/oak/bin/oakcli deploy), loading the configuration from your file or entering all information from there. Crossing the fingers, this should go to the end without any problem. On the opposite, My Oracle Support notes may help. The nice thing with ODA is that most of the configurations are similar so there a good chances that a problem was already encountered and documented.

Cet article ODA X6 installation: re-image est apparu en premier sur Blog dbi services.

 
The process of examining sets of data using specialized computer systems is called data analytics or data analysis. These computer systems make data easier to interpret by transforming, arranging, and modeling it to form patterns.

Data analytics tools guide businesspeople in coming up with better business decisions. Researchers and scientists also use these tools to evaluate scientific hypotheses, theories, and models.

Real-time report of data about the performance of a company, a specific department, a project, or group of employees can be accessed through a so-called data analytics dashboard. This is an information management tool, which monitors a group or a company’s metrics, key data points, and key performance indicators (KPI).

A dashboard can be customized according to a department or a company’s needs. It connects to your attachments, services, files, and Application Program Interface (API).

IT Management Dashboards

Some of the available dashboards for IT include the following:

Read more at http://www.infocaptor.com/dashboard/data-analytics-and-benefits-of-dashboards-for-it

In Oracle E-Business Suite, concurrent processing simultaneously executes programs running in the background with online operations. When a user runs a report, a request to run the report is generated. The command to run the report is a concurrent request. The program that generates the report is a concurrent program. Concurrent programs are started by a concurrent manager.

A new CPADMIN command line utility for E-Business Suite 12.2 consolidates various utilities for concurrent processing into a single menu-based utility. This ADADMIN-style utility can be used for multiple tasks, including:

• View Concurrent Manager status
• Clean CP tables
• Set Concurrent Manager diagnostics
• Start, stop, or verify an individual Concurrent Manager
• Rebuild Concurrent Manager views
• Move request files
• Analyze requests
• Configure request log/out file directory locations

Complete details for running the new CPADMIN utility are published here:

• Concurrent Processing Command-Line Utility (EBS 12.2 Setup Guide)

Related Articles

• Where should EBS Concurrent Managers be located?
• Webcast: Performance Tuning E-Business Suite Concurrent Manager

We are pleased to announce the availability of new content for the Oracle Functional Testing Advanced Pack for Oracle Utilities. This pack allows customers of supported Oracle Utilities products to adopt automated testing quickly and easily by providing the testing components used by Product Development for use in the Oracle Application Testing Suite.

We have released, as patches available from My Oracle Support, the following content patches:

• Oracle Utilities Customer Care And Billing v2.6.0.0.0 (available as patch 26075747).
• Oracle Utilities Customer To Meter v2.6.0.0.0 (available as patch 26075823).
• Oracle Utilities Meter Data Management/ Oracle Utilities Smart Grid Gateway v2.2.0.1 (available as patch 26075799).

This means the current release of the pack, v5.0.1.0, supports the following products and versions:

• Oracle Utilities Customer Care And Billing 2.4.0.3, 2.5.0.1, 2.5.0.2 & 2.6.0.0
• Oracle Utilities Mobile Workforce Management 2.2.0.3, 2.3.0.0 & 2.3.0.1
• Oracle Real Time Scheduler 2.2.0.3, 2.3.0.0 & 2.3.0.1
• Oracle Utilities Application Framework 4.2.0.3, 4.3.0.1, 4.3.0.2, 4.3.0.3 & 4.3.0.4
• Oracle Utilities Meter Data Management 2.1.0.3, 2.2.0.0 & 2.2.0.1
• Oracle Utilities Smart Grid Gateway (all adapters) 2.1.0.3, 2.2.0.0 & 2.2.0.1      
• Oracle Utilities Work And Asset Management 2.1.1, & 2.2.0
• Oracle Utilities Operational Device Management 2.1.1 & 2.2.0
• Oracle Utilities Customer To Meter 2.6.0.0

The pack continues to support the ability to build flows for these products, including flows across multiple products, packaged integration and supports all channels of access including online, web services and batch. We also support mobile testing for the Oracle Utilities Mobile Workforce Management and Oracle Real Time Scheduler products running on Android and iOS devices.

The pack also includes sanity flows used by the Oracle Utilities cloud deployments that test the installation of the products are complete and operational.

It is hot in Europe, it is summer, enjoy, but technology moves fast so you have the chance to already prepare for the next conferences. The IT Tage 2017 will happen the 11th to 14th of December this year and we are happy to be there again.

This event covers a wide range of topics and we will be there again covering and talking about:

• Stéphane Haby, SQL Server 2017: Überblick
• Stéphane Haby, SQL Server: Sicherheit mit Policies
• Natascha Karfich, Vagrant Up – Aufbau einer kompletten Oracle-Test-Infrastruktur mit Vagrant und Ansible
• David Barbarin, SQL Server: Hochverfügbarkeit auf Linux
• Daniel Westermann, PostgreSQL-Upgrade: Best Practices

In addition you will have the chance to join Jan from EnterpriseDB speaking about the differences between Oracle and PostgreSQL. If you want to hear more about that, you might want to join the PostgreSQL Conference Europe this year.

Maybe Jan and me get the chance to talk there as well, we submitted an interesting session, stay tuned.

Chances are high that you may find us at the ukoug, too:

… and we’ll be at the #DOAG2017 for sure this year again.

Hope to see you soon… Cheers, discussions ahead …

Cet article Summer, autumn and winter: a lot of conferences ahead est apparu en premier sur Blog dbi services.

I described in an earlier post on AWR views how the dictionary views were using metadata and object links to show information from other containers. But this mechanism cannot work for fixed views (aka V$) because they don’t have their definition in the dictionary.

The big difference is that most of V$ views are available long before the dictionary is opened or even created. Just start an instance in NOMOUNT and you can query the V$ views. Even in multitenant, you can switch to different containers in MOUNT, and query V$ views, when no dictionary is opened.

SQL> alter database mount;
Database altered.
 
SQL> show pdbs
 
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED MOUNTED
3 PDB1 MOUNTED
 
SQL> alter session set container=pdb1;
Session altered.
 
SQL> show pdbs;
 
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
3 PDB1 MOUNTED

V$ views query information from the instance and this information pertain to one container:

• CON_ID=0 for the CDB itself
• CON_ID=1 for CDB$ROOT
• CON_ID=2 for PDB$SEED
• CON_ID=3 for the first PDB you have created

When you are in root, the V$ views are queried as normal and show all information – from all containers – with their related CON_ID

When you are in a PDB, you must see the objects that belong to your PDB, but not those that belong to other PDBS. But this is not sufficient. For example, you may query the version, and the version is related to the CDB itself, with CON_ID=0:

SQL> alter session set container=CDB$ROOT;
Session altered.
 
SQL> select * from v$version;
 
BANNER CON_ID
-------------------------------------------------------------------------------- ----------
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production 0
PL/SQL Release 12.2.0.1.0 - Production 0
CORE 12.2.0.1.0 Production 0
TNS for Linux: Version 12.2.0.1.0 - Production 0
NLSRTL Version 12.2.0.1.0 - Production 0

Then, in a PDB you should see your PDB objects and the CON_ID=0 ones. Oracle needs a new mecanism for that. One way would be to switch to root, query the V$ and filter on CON_ID. We don’t need that. Context switch is there to access data from a different container tablespace, because tablepaces are not shared. But V$ views expose data from the instance, and the instance is shared. Any container can see all rows, and we just want to filter some rows.

Here is the execution plan when querying V$VERSION from a PDB:


SQL> connect sys/oracle@//localhost/PDB1 as sysdba
Connected.
SQL> explain plan for select * from v$version;
Explained.
 
SQL> select * from table(dbms_xplan.display);
PLAN_TABLE_OUTPUT
Plan hash value: 1078166315
 
------------------------------------------------------------------------------
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
------------------------------------------------------------------------------
| 0 | SELECT STATEMENT | | 1 | 68 | 0 (0)| 00:00:01 |
|* 1 | FIXED TABLE FULL| X$VERSION | 1 | 68 | 0 (0)| 00:00:01 |
------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
1 - filter(("CON_ID"=0 OR "CON_ID"=3) AND
"INST_ID"=USERENV('INSTANCE'))


An additional predicate (“CON_ID”=0 OR “CON_ID”=3) is added to the view. How is it done? Oracle has a security feature for that: Virtual Private Database – aka Row Level Security – which adds a where clause dynamically.

One way to get more information about virtual private databases is to have an error on its execution and I know that a user with only select privilege cannot EXPLAIN PLAN (see MOS Note 1029064.6).

I connect to a PDB with a low privileged user:
SQL> connect scott/tiger@//localhost/PDB1
Connected.

I explain plan the V$VERSION fixed view.
SQL> explain plan for select * from v$version;
 
Error starting at line : 10 File @ /media/sf_share/122/blogs/multitenant-vpd.sql
In command -
explain plan for select * from v$version
Error report -
ORA-28113: policy predicate has error
28113. 00000 - "policy predicate has error"
*Cause: Policy function generates invalid predicate.
*Action: Review the trace file for detailed error information.


Interesting error which confirms the guess: this is a VPD error and it generates a trace:
*** 2017-06-26T22:45:17.838507+02:00 (PDB1(3))
*** SESSION ID:(141.17865) 2017-06-26T22:45:17.838537+02:00
*** CLIENT ID:() 2017-06-26T22:45:17.838541+02:00
*** SERVICE NAME:(pdb1) 2017-06-26T22:45:17.838545+02:00
*** MODULE NAME:(java@VM104 (TNS V1-V3)) 2017-06-26T22:45:17.838548+02:00
*** ACTION NAME:() 2017-06-26T22:45:17.838552+02:00
*** CLIENT DRIVER:(jdbcoci : 12.2.0.1.0) 2017-06-26T22:45:17.838555+02:00
*** CONTAINER ID:(3) 2017-06-26T22:45:17.838558+02:00
 
-------------------------------------------------------------
Error information for ORA-28113:
Logon user : SCOTT
Table/View : SYS.V_$VERSION
VPD Policy name : CON_ID
Policy function: SYS.CON_ID
RLS view :
SELECT "BANNER","CON_ID" FROM "SYS"."V_$VERSION" "V_$VERSION" WHERE (con_id IN (0, 3) )
ORA-01039: insufficient privileges on underlying objects of the view
-------------------------------------------------------------

There’s no container switch here, all is running in PDB1 with CON_ID=3 and the internal VPD has added a where clause to filter rows with CON_ID=0 and CON_ID=3

Do not search for the VPD policy name ‘CON_ID’ and function ‘CON_ID’ in the dictionary views because this happens even when the dictionary is not accessible. This is an internal policy used when querying fixed views in multitenant and which probably use some of the VPD code only.

Cet article 12c Multitenant Internals: VPD for V$ views est apparu en premier sur Blog dbi services.