Feed aggregator

12cR2: How long to upgrade a PDB?

Yann Neuhaus - Sun, 2016-11-20 09:39

In the previous post I described how simple it is to unplug a PDB and plug it into a newer version CDB. One goal of dictionary separation in the multitenant architecture is to keep system objects on CDB$ROOT only. Knowing that an upgrade does not touch the application metadata and data, does this make PDB upgrade fast as a simple refresh of metadata links?

CDB$ROOT upgrade

As a point of comparison I’ve run an upgrade on an empty CDB from 12.1.0.2 to 12.2.0.1 and here is the summary:

Oracle Database 12.2 Post-Upgrade Status Tool 11-19-2016 14:04:51
[CDB$ROOT]  
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
 
Oracle Server UPGRADED 12.2.0.1.0 00:11:19
JServer JAVA Virtual Machine UPGRADED 12.2.0.1.0 00:04:29
Oracle Real Application Clusters UPGRADED 12.2.0.1.0 00:00:00
Oracle Workspace Manager UPGRADED 12.2.0.1.0 00:00:41
OLAP Analytic Workspace UPGRADED 12.2.0.1.0 00:00:14
Oracle OLAP API UPGRADED 12.2.0.1.0 00:00:08
Oracle Label Security UPGRADED 12.2.0.1.0 00:00:05
Oracle XDK UPGRADED 12.2.0.1.0 00:01:01
Oracle Text UPGRADED 12.2.0.1.0 00:00:31
Oracle XML Database UPGRADED 12.2.0.1.0 00:01:33
Oracle Database Java Packages UPGRADED 12.2.0.1.0 00:00:07
Oracle Multimedia UPGRADED 12.2.0.1.0 00:01:22
Spatial UPGRADED 12.2.0.1.0 00:04:46
Oracle Application Express VALID 5.0.0.00.31 00:00:02
Oracle Database Vault UPGRADED 12.2.0.1.0 00:00:15
Final Actions 00:01:50
Post Upgrade 00:00:12
 
Total Upgrade Time: 00:29:17 [CDB$ROOT]

This was running on a Oracle Public Cloud DBaaS with two OCPUs which means four threads. It’s about 30 minutes to upgrade the system dictionary and all components.
Those are the times we are used to. Since 12c some operations are parallelized to make it faster than in previous versions.

The more components you install, the longer it takes. Even if it is recommended to install all components in a CDB in case a PDB needs it, you may think about this.

PDB upgrade

When you plug a PDB, you should not have all this work to do. You can expect that the metadata links and data links just work, now pointing to the new version. At most, a quick check or refresh may be necessary to ensure that object types did not change.

At UKOUG TECH16 in 12c Multitenant: Not a Revolution, Just an Evolution I demo how those links work internally and I show that running a full CATUPGRD.SQL on each container is not required to be run for each object. However, the DBUPGRADE script runs it. Let’s see if it is optimized for pluggable databases.

In 12.2 the command is easy:

[oracle@HP122A tmp]$ $ORACLE_HOME/bin/dbupgrade -c PDB1

You can see that it runs the catctl.pl commands that we used in 12.1

Start processing of PDB1
[/u01/app/oracle/product/12.2.0/dbhome_1/perl/bin/perl /u01/app/oracle/product/12.2.0/dbhome_1/rdbms/admin/catctl.pl -c 'PDB1' -I -i pdb1 -n 2 -l /home/oracle /u01/app/oracle/product/12.2.0/dbhome_1/rdbms/admin/catupgrd.sql]

Here is what will be run.

Number of Cpus = 2
Database Name = HP122A
DataBase Version = 12.2.0.1.0
Generated PDB Inclusion:[PDB1] CDB$ROOT Open Mode = [OPEN] Components in [PDB1] Installed [APEX APS CATALOG CATJAVA CATPROC CONTEXT DV JAVAVM OLS ORDIM OWM SDO XDB XML XOQ] Not Installed [EM MGW ODM RAC WK]

Summary is here:

Oracle Database 12.2 Post-Upgrade Status Tool 11-19-2016 15:25:15
[PDB1]  
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
 
Oracle Server UPGRADED 12.2.0.1.0 00:08:59
JServer JAVA Virtual Machine UPGRADED 12.2.0.1.0 00:02:16
Oracle Real Application Clusters UPGRADED 12.2.0.1.0 00:00:00
Oracle Workspace Manager UPGRADED 12.2.0.1.0 00:00:27
OLAP Analytic Workspace UPGRADED 12.2.0.1.0 00:00:22
Oracle OLAP API UPGRADED 12.2.0.1.0 00:00:07
Oracle Label Security UPGRADED 12.2.0.1.0 00:00:03
Oracle XDK UPGRADED 12.2.0.1.0 00:00:40
Oracle Text UPGRADED 12.2.0.1.0 00:00:18
Oracle XML Database UPGRADED 12.2.0.1.0 00:01:25
Oracle Database Java Packages UPGRADED 12.2.0.1.0 00:00:03
Oracle Multimedia UPGRADED 12.2.0.1.0 00:01:13
Oracle Application Express VALID 5.0.0.00.31 00:00:02
Oracle Database Vault UPGRADED 12.2.0.1.0 00:00:40
Final Actions 00:01:49
Post Upgrade 00:01:17
 
Total Upgrade Time: 00:23:55 [PDB1]  
Database time zone version is 18. It is older than current release time
zone version 26. Time zone upgrade is needed using the DBMS_DST package.
 
Grand Total Upgrade Time: [0d:0h:25m:0s]

When you compare with a CDB$ROOT upgrade the gain is very small. We saved 25% of Oracle Server time. JVM and XDK was x2 faster. But finally, that’s only 5 minutes.

It is important to understand that the upgrade time depends on the components installed. Here is the percentage of time per component:

CapturedbupgradePDB

About the core of the database, what we know as catalog/catproc, here is the detail showing which phases are run in parallel.
Note that the phase number is important because in 12.2 you can restart a failed upgrade from where it stopped.


------------------------------------------------------
Phases [0-117] Start Time:[2016_11_19 15:00:37] Container Lists Inclusion:[PDB1] Exclusion:[NONE] ------------------------------------------------------
*********** Executing Change Scripts ***********
Serial Phase #:0 [PDB1] Files:1 Time: 36s
*************** Catalog Core SQL ***************
Serial Phase #:1 [PDB1] Files:5 Time: 39s
Restart Phase #:2 [PDB1] Files:1 Time: 1s
*********** Catalog Tables and Views ***********
Parallel Phase #:3 [PDB1] Files:19 Time: 23s
Restart Phase #:4 [PDB1] Files:1 Time: 0s
************* Catalog Final Scripts ************
Serial Phase #:5 [PDB1] Files:6 Time: 15s
***************** Catproc Start ****************
Serial Phase #:6 [PDB1] Files:1 Time: 12s
***************** Catproc Types ****************
Serial Phase #:7 [PDB1] Files:2 Time: 9s
Restart Phase #:8 [PDB1] Files:1 Time: 0s
**************** Catproc Tables ****************
Parallel Phase #:9 [PDB1] Files:70 Time: 48s
Restart Phase #:10 [PDB1] Files:1 Time: 1s
************* Catproc Package Specs ************
Serial Phase #:11 [PDB1] Files:1 Time: 12s
Restart Phase #:12 [PDB1] Files:1 Time: 1s
************** Catproc Procedures **************
Parallel Phase #:13 [PDB1] Files:97 Time: 8s
Restart Phase #:14 [PDB1] Files:1 Time: 1s
Parallel Phase #:15 [PDB1] Files:118 Time: 11s
Restart Phase #:16 [PDB1] Files:1 Time: 1s
Serial Phase #:17 [PDB1] Files:13 Time: 3s
Restart Phase #:18 [PDB1] Files:1 Time: 1s
***************** Catproc Views ****************
Parallel Phase #:19 [PDB1] Files:33 Time: 25s
Restart Phase #:20 [PDB1] Files:1 Time: 0s
Serial Phase #:21 [PDB1] Files:3 Time: 8s
Restart Phase #:22 [PDB1] Files:1 Time: 1s
Parallel Phase #:23 [PDB1] Files:24 Time: 82s
Restart Phase #:24 [PDB1] Files:1 Time: 1s
Parallel Phase #:25 [PDB1] Files:11 Time: 42s
Restart Phase #:26 [PDB1] Files:1 Time: 0s
Serial Phase #:27 [PDB1] Files:1 Time: 0s
Serial Phase #:28 [PDB1] Files:3 Time: 5s
Serial Phase #:29 [PDB1] Files:1 Time: 0s
Restart Phase #:30 [PDB1] Files:1 Time: 0s
*************** Catproc CDB Views **************
Serial Phase #:31 [PDB1] Files:1 Time: 2s
Restart Phase #:32 [PDB1] Files:1 Time: 1s
Serial Phase #:34 [PDB1] Files:1 Time: 0s
***************** Catproc PLBs *****************
Serial Phase #:35 [PDB1] Files:283 Time: 17s
Serial Phase #:36 [PDB1] Files:1 Time: 0s
Restart Phase #:37 [PDB1] Files:1 Time: 0s
Serial Phase #:38 [PDB1] Files:1 Time: 3s
Restart Phase #:39 [PDB1] Files:1 Time: 1s
*************** Catproc DataPump ***************
Serial Phase #:40 [PDB1] Files:3 Time: 49s
Restart Phase #:41 [PDB1] Files:1 Time: 1s
****************** Catproc SQL *****************
Parallel Phase #:42 [PDB1] Files:13 Time: 51s
Restart Phase #:43 [PDB1] Files:1 Time: 0s
Parallel Phase #:44 [PDB1] Files:12 Time: 8s
Restart Phase #:45 [PDB1] Files:1 Time: 1s
Parallel Phase #:46 [PDB1] Files:2 Time: 2s
Restart Phase #:47 [PDB1] Files:1 Time: 1s
************* Final Catproc scripts ************
Serial Phase #:48 [PDB1] Files:1 Time: 5s
Restart Phase #:49 [PDB1] Files:1 Time: 1s
************** Final RDBMS scripts *************
Serial Phase #:50 [PDB1] Files:1 Time: 16s

In the summary when we compare with a CDB$ROOT upgrade we don’t see the Spatial part that took 4 minutes but we see it in the detail:

***************** Upgrading SDO ****************
Restart Phase #:81 [PDB1] Files:1 Time: 1s
Serial Phase #:83 [PDB1] Files:1 Time: 23s
Serial Phase #:84 [PDB1] Files:1 Time: 4s
Restart Phase #:85 [PDB1] Files:1 Time: 1s
Serial Phase #:86 [PDB1] Files:1 Time: 5s
Restart Phase #:87 [PDB1] Files:1 Time: 0s
Parallel Phase #:88 [PDB1] Files:3 Time: 110s
Restart Phase #:89 [PDB1] Files:1 Time: 0s
Serial Phase #:90 [PDB1] Files:1 Time: 4s
Restart Phase #:91 [PDB1] Files:1 Time: 1s
Serial Phase #:92 [PDB1] Files:1 Time: 4s
Restart Phase #:93 [PDB1] Files:1 Time: 0s
Parallel Phase #:94 [PDB1] Files:4 Time: 30s
Restart Phase #:95 [PDB1] Files:1 Time: 0s
Serial Phase #:96 [PDB1] Files:1 Time: 3s
Restart Phase #:97 [PDB1] Files:1 Time: 1s
Serial Phase #:98 [PDB1] Files:1 Time: 22s
Restart Phase #:99 [PDB1] Files:1 Time: 0s
Serial Phase #:100 [PDB1] Files:1 Time: 3s
Restart Phase #:101 [PDB1] Files:1 Time: 1s
Serial Phase #:102 [PDB1] Files:1 Time: 2s
Restart Phase #:103 [PDB1] Files:1 Time: 1s

So what?

From what we see, the multitenant architecture, with consolidation of the system directory in only one place – the CDB$ROOT – we have no gain in upgrade. In the current implementation (12.2.0.1) the same work is done on all containers, with only minimal optimization for pluggable databases where we have metadata links instead of full object metadata.
In summary:

  • Upgrading by plug-in or remote clone is faster than upgrading the whole CDB because CDB has more containers, such as PDB$SEED
  • But upgrading a single PDB, whatever the method is, is not faster than upgrading a non-CDB

I’m talking about upgrade of the container here. Transportable tablespaces/database is a different thing.

More about the Multitenant internals, dictionary separation, metadata links and data links (was called object links in 12.1) at UKOUG TECH 2016 conference next month.

CaptureUpgradePres

 

Cet article 12cR2: How long to upgrade a PDB? est apparu en premier sur Blog dbi services.

Flashback Database -- 3 : Purging (older) Flashback Logs

Hemant K Chitale - Sun, 2016-11-20 08:34
As demonstrated earlier, Oracle may maintain Flashback Logs for a duration that is longer than the Flashback Retention Target.  This can happen when the db_recovery_filie_dest_size is large enough to support them (along with ArchiveLogs, Backups etc)

For example, in my play database I have reset the retention target to 1day but the Flashback Logs exceed 4 days :

SQL> show parameter flashback_ret

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_flashback_retention_target integer 1440
SQL> select sysdate-oldest_flashback_time from v$flashback_database_log;

SYSDATE-OLDEST_FLASHBACK_TIME
-----------------------------
4.21686343



The DBA should not manually delete Flashback Logs.

The only way I've found to purge older Flashback Logs is to reset db_recovery_file_dest_size to a lower value such that current FRA usage exceeds the dest_size.  This prompts Oracle to purge older Flashback Logs.

However, if ArchiveLogs exist and consume significant space and frequncy in the FRA, you do run the risk of

ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance orcl - Archival Error
ORA-16038: log 1 sequence# nnn cannot be archived
ORA-19809: limit exceeded for recovery files

and/or

ORACLE Instance orcl- Cannot allocate log, archival required
Thread 1 cannot allocate new log, sequence nnn
All online logs need archiving
Examine archive trace files for archiving errors


errors.
So, be careful to monitor your FRA usage and the Flashback Logs.  Use V$FLASHBACK_DATABASE_LOG, V$FLASHBACK_DATABASE_LOGFILE, V$FLASHBACK_DATABASE_STAT and V$FLASH_RECOVERY_AREA_USAGE view.
(see my earlier post that also points to an Oracle Support Doc about the first two views).
.
.
.


Categories: DBA Blogs

Why I get different results when comparing scalar type collection populated in PLSQL but not when it is populated in SQL

Tom Kyte - Sun, 2016-11-20 04:26
Hi guys, I'm running on Oracle Database 11g Express Edition Release 11.2.0.2.0 - 64bit Production I started getting very strange results when doing collection data comparison within PLSQL. I've managed to narrow down the issue to a test case bel...
Categories: DBA Blogs

Pipelined function does not handle collection function calls properly

Tom Kyte - Sun, 2016-11-20 04:26
Hi, When using a pipelined function that calls another function, returning a collection I get wrong results. Here is an isolated test case <code> select * from v$version; create or replace type an_array as table of varchar2(32767); / cre...
Categories: DBA Blogs

Will PL/SQL language support real OO programming in the future?

Tom Kyte - Sun, 2016-11-20 04:26
There are always a lot of discussion & argument regarding whether to implement business rules inside the database, (i.e., close to the data, using PL/SQL) or outside the database (e.g. in the mid-tier, using Java or other language). I used to support...
Categories: DBA Blogs

Behavior of Oracle VPD considering Stored Procedures

Tom Kyte - Sun, 2016-11-20 04:26
Hi Tom, I have a particular question related to Oracle VPD (Virtual Private Database) behavior in case of Stored Procedures. I tried searching in Oracle Documentation as well as in the questions answered in AskTom, but couldn't find anything that...
Categories: DBA Blogs

DOAG 2016 - "Oracle Database Cloud Performance" presentation material

Randolf Geist - Sat, 2016-11-19 15:23
Thanks to all attendees that came to my presentation "Oracle Database Cloud Performance" at the DOAG conference 2016. You can check the presentation material here at Slideshare.

12cR2: Upgrade by unplug/plug in the Oracle Cloud Service

Yann Neuhaus - Sat, 2016-11-19 15:01

12.2 is available in the Oracle Public Cloud DBaaS. If you have a 12.1 DBaaS service, there’s no button to upgrade it. I’ll describe all the possible upgrade procedures and the first one, and the most simple, is to create a new DBaaS service in 12.2 and unplug/plug the PDBs to it.

Here is my DBaaS in 12.1

[oracle@HP121A ~]$ sqlplus / as sysdba
 
SQL*Plus: Release 12.1.0.2.0 Production on Sat Nov 19 14:47:04 2016
 
Copyright (c) 1982, 2014, Oracle. All rights reserved.
 
 
Connected to:
Oracle Database 12c EE High Perf Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Advanced Analytics
and Real Application Testing options
 
SQL> show pdbs
 
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB1 READ WRITE NO

Unplug

I close the PDB1 and unplug it.

SQL> alter pluggable database PDB1 close;
 
Pluggable database altered.
 
SQL> alter pluggable database PDB1 unplug into '/tmp/PDB1.xml';
 
Pluggable database altered.

Copy files

I’ve opened ssh between the two VMs and copy the xml file
[oracle@HP122A tmp]$ scp 141.144.32.166:/tmp/PDB1.xml .
The authenticity of host '141.144.32.168 (141.144.32.168)' can't be established.
RSA key fingerprint is 84:e4:e3:db:67:20:e8:e2:f7:ff:a6:4d:9e:ee:a4:08.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '141.144.32.168' (RSA) to the list of known hosts.
PDB1.xml 100% 6118 6.0KB/s 00:00

From the xml file I see which files are referenced:
[oracle@HP121A ~]$ grep path /tmp/PDB1.xml
<path>/u02/app/oracle/oradata/HP121A/41A8A48F54195236E0534EC5C40A569E/datafile/o1_mf_system_d30owr5v_.dbf</path>
<path>/u02/app/oracle/oradata/HP121A/41A8A48F54195236E0534EC5C40A569E/datafile/o1_mf_sysaux_d30owr69_.dbf</path>
<path>/u02/app/oracle/oradata/HP121A/41A8A48F54195236E0534EC5C40A569E/datafile/o1_mf_temp_d30owr6h_.dbf</path>

and copy them

[oracle@HP122A tmp]$ scp -r 141.144.32.168:/u02/app/oracle/oradata/HP121A/41A8A48F54195236E0534EC5C40A569E /u02/app/oracle/oradata/HP121A
o1_mf_temp_d30owr6h_.dbf 100% 20MB 20.0MB/s 00:00
o1_mf_system_d30owr5v_.dbf 100% 270MB 135.0MB/s 00:02
o1_mf_sysaux_d30owr69_.dbf 100% 570MB 114.0MB/s 00:05

Plug

It’s only one command to plug it into the 12.2 CDB:

[oracle@HP122A tmp]$ sqlplus / as sysdba
 
SQL*Plus: Release 12.2.0.1.0 Production on Sat Nov 19 14:50:26 2016
 
Copyright (c) 1982, 2016, Oracle. All rights reserved.
 
Connected to:
Oracle Database 12c EE High Perf Release 12.2.0.1.0 - 64bit Production
 
SQL> show pdbs
 
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
 
SQL> create pluggable database PDB1 using '/tmp/PDB1.xml';
Pluggable database created.

At that time, you can drop it from the source but probably you will remove the service once you are sure the migration is ok.

Upgrade

That was easy, but that was only the transportation of the PDB to another CDB, but it cannot be opened so easily on a newer version CDB. When we open the PDB we get a warning:
SQL> alter pluggable database PDB1 open;
 
Warning: PDB altered with errors.

and have to look at the PDB_PLUG_IN_VIOLATIONS

SQL> select MESSAGE from pdb_plug_in_violations order by time
 
MESSAGE
-----------------------------------------------------------------------------------------------------------
APEX mismatch: PDB installed version NULL CDB installed version 5.0.4.00.12
CDB is using local undo, but no undo tablespace found in the PDB.
CDB parameter compatible mismatch: Previous '12.1.0.2.0' Current '12.2.0'
Database option APS mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option CATALOG mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option CATJAVA mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option CATPROC mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option CONTEXT mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option DV mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option JAVAVM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option OLS mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option ORDIM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option OWM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option SDO mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option XDB mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option XML mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
Database option XOQ mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.
PDB's version does not match CDB's version: PDB's version 12.1.0.2.0. CDB's version 12.2.0.1.0.

Each component report a newer version. We have to upgrade them running catupgrd.sql.
In 12.2 we have a new script that calls the catctl.pl and catupgrd.sql to make this easier. It is a shell script located in ORACLE_HOME/bin and is dbupgrade. As with catcon.pl we have the ‘-c’ argument to run it on PDB1:

[oracle@HP122A tmp]$ $ORACLE_HOME/bin/dbupgrade -c PDB1

How long does it take? Documentation says that:
It is easier to apply a patch to one CDB than to multiple non-CDBs and to upgrade one CDB than to upgrade several non-CDBs.
So this supposes that upgrade work is mostly done at CDB level. PDBs have only metadata links to them. It’s only a virtual dictionary.

More than 3 years after the multitenant architecture was released, there are big doubts about the time it takes to upgrade a PDB plugged from a previous version:

#dbupgrade @OracleDatabase
Guess how many minutes to catupgrd a 12.1 PDB plugged into an empty 12.2 CDB?
[ doc says https://t.co/hQTknmKl1y

— Franck Pachot (@FranckPachot) November 19, 2016

So I keep the answer for the next blog post.

 

Cet article 12cR2: Upgrade by unplug/plug in the Oracle Cloud Service est apparu en premier sur Blog dbi services.

Amazon Web Services: Upgrade to Dbvisit Standby 8

Yann Neuhaus - Sat, 2016-11-19 12:51

In a previous blog we installed Dbvisit Standby 7 on two AWS linux instances. In this article we are just upgrading to Dbvisit Standby 8. The first thing is to stop on both nodes dbvnet and dbvserver on both servers

[oracle@primaserver dbvnet]$ ps -ef|grep dbv|grep -v grep
oracle 2062 1 0 04:53 ? 00:00:02 /u01/app/dbvisit/dbvserver/dbvserverd
oracle 2064 2062 0 04:53 ? 00:00:00 /u01/app/dbvisit/dbvserver/dbvserverd
oracle 2131 1 0 04:54 ? 00:00:00 /u01/app/dbvisit/dbvnet/dbvnetd
oracle 2132 2131 0 04:54 ? 00:00:00 /u01/app/dbvisit/dbvnet/dbvnetd
oracle 2142 2131 0 04:54 ? 00:00:00 /u01/app/dbvisit/dbvnet/dbvnetd
oracle 2143 2131 0 04:54 ? 00:00:00 /u01/app/dbvisit/dbvnet/dbvnetd
oracle 2144 2131 0 04:54 ? 00:00:00 /u01/app/dbvisit/dbvnet/dbvnetd
oracle 4036 2062 0 08:03 ? 00:00:01 /u01/app/dbvisit/dbvserver/dbvserverd
oracle 4037 2062 0 08:03 ? 00:00:02 /u01/app/dbvisit/dbvserver/dbvserverd


[oracle@primaserver dbvnet]$ pwd
/u01/app/dbvisit/dbvnet
[oracle@primaserver dbvnet]$ ./dbvnetd stop
[oracle@primaserver dbvnet]$ cd ../dbvserver/
[oracle@primaserver dbvserver]$ ./dbvserverd stop
[oracle@primaserver dbvserver]$

The upgrade is done by launching dbvisit installer and must be done on both servers. The upgrade process consist out of two steps:
1-Upgrade (install) the new version 8 software
2- Upgrade the version 7 DDC files
It is important to take into account that Dbvisit Standby version 8 makes use of a central web based user interface (GUI). The GUI is no longer installed on each of the Database Servers being managed.So during the upgrade we will remove the current Dbvserver installation and will Install the Dbvisit Standby Core Components – Dbvagent, Dbvnet and Dbvisit Standby CLI

Let’s launch install-dbvisit executable

[oracle@primaserver installer]$ ./install-dbvisit
-----------------------------------------------------------
Welcome to the Dbvisit software installer.
-----------------------------------------------------------
It is recommended to make a backup of our current Dbvisit software
location (Dbvisit Base location) for rollback purposes.
Installer Directory /home/oracle/dbvisit/dbvisit8/dbvisit
>>> Please specify the Dbvisit installation directory (Dbvisit Base).
The various Dbvisit products and components - such as Dbvisit Standby,
Dbvisit Dbvnet will be installed in the appropriate subdirectories of
this path.
Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
> /u01/app/dbvisit
DBVISIT_BASE = /u01/app/dbvisit
-----------------------------------------------------------
Component Installer Version Installed Version
-----------------------------------------------------------
standby 8.0.04.18184 7.0.62.16992
dbvnet 2.0.04.18184 7
dbvagent 2.0.04.18184 not installed
dbvserver 2.0.04.18184 7
-----------------------------------------------------------
What action would you like to perform?
1 - Install component(s)
2 - Uninstall component(s)
3 - Terminate
Your choice: 2
Which component do you want to install?
1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
2 - Dbvisit Standby Core (Command Line Interface)
3 - Dbvnet (Dbvisit Network Communication)
4 - Dbvagent (Dbvisit Agent)
5 - Dbvserver (Dbvisit Central Console)
6 - Exit Installer
Your choice: 5
Component dbvserver uninstalled.
-----------------------------------------------------------
Component Installer Version Installed Version
-----------------------------------------------------------
standby 8.0.04.18184 7.0.62.16992
dbvnet 2.0.04.18184 7
dbvagent 2.0.04.18184 not installed
dbvserver 2.0.04.18184 not installed
-----------------------------------------------------------
What action would you like to perform?
1 - Install component(s)
2 - Uninstall component(s)
3 - Terminate
Your choice: 1
Which component do you want to install?
1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
2 - Dbvisit Standby Core (Command Line Interface)
3 - Dbvnet (Dbvisit Network Communication)
4 - Dbvagent (Dbvisit Agent)
5 - Dbvserver (Dbvisit Central Console)
6 - Exit Installer
Your choice: 1
-----------------------------------------------------------
Summary of the Dbvisit STANDBY configuration
-----------------------------------------------------------
DBVISIT_BASE /u01/app/dbvisit
Press ENTER to continue
-----------------------------------------------------------
About to configure DBVISIT DBVNET
-----------------------------------------------------------
>>> Please specify the Local host name to be used by Dbvnet on this server.
Dbvnet will be listening on the local IP Address on this server which
resolve to the host name specified here.
If using a cluster or virtual IP make sure the host name or alias
specified here resolve to the IP address local to where dbvnet is
installed.
Enter a custom value or press ENTER to accept default [primaserver]:
>
>>> Please specify the Local Dbvnet PORT to be used.
Dbvnet will be listening on the specified port for incoming connections
from remote dbvnet connections. Please make sure that this port is not
already in use or blocked by any firewall. You may choose any value
between 1024 and 65535, however the default of 7890 is recommended.
Enter a custom value or press ENTER to accept default [7890]:
>
>>> Please specify the Remote host name to be used by Dbvnet.
By default Dbvnet will use this remote hostname for any remote
connections. Dbvnet must be installed and configured on the specified
remote host. If using a cluster or virtual IP make sure the host name
or alias specified here resolve to the IP address local to where dbvnet
is installed.
If you are unsure about the remote host name during installation, use
the default value which will be the current local hostname.
Enter a custom value or press ENTER to accept default [primaserver]:
> standserver
>>> Please specify the Remote Dbvnet PORT to be used.
Dbvnet will connect to the remote server on this specified port.
On the remote host Dbvnet will be listening on the specified port for
incoming connections. Please make sure that this port is not already in
use or blocked by any firewall. You may choose any value between 1024
and 65535, however the default of 7890 is recommended.
Enter a custom value or press ENTER to accept default [7890]:
>
>>> Please specify the Dbvnet Passphrase to be used for secure connections.
The passphrase provided must be the same in both the local and remote
Dbvnet installations. It is used to establish a secure (encrypted)
Dbvnet connections
Enter a custom value:
> root
-----------------------------------------------------------
Summary of the Dbvisit DBVNET configuration
-----------------------------------------------------------
DBVISIT_BASE /u01/app/dbvisit
DBVNET_LOCAL_HOST primaserver
DBVNET_LOCAL_PORT 7890
DBVNET_REMOTE_HOST standserver
DBVNET_REMOTE_PORT 7890
DBVNET_PASSPHRASE root
Press ENTER to continue
About to configure DBVISIT DBVAGENT
-----------------------------------------------------------
>>> Please specify the host name to be used for the Dbvisit Agent.
The Dbvisit Agent (Dbvagent) will be listening on this local address.
If you are using the Dbvserver (GUI) - connections from the GUI will be
established to the Dbvisit Agent. The Dbvisit Agent address must be
visible from the Dbvserver (GUI) installation.
If using a cluster or virtual IP make sure the host name or alias
specified here resolve to the IP address local to where dbvnet is
installed.
Enter a custom value or press ENTER to accept default [primaserver]:
>
>>> Please specify the listening PORT number for Dbvagent.
The Dbvisit Agent (Dbvagent) will listening on the specified port for
incoming requests from the GUI (Dbvserver). Please make sure that this
port is not already in use or blocked by any firewall. You may choose
any value between 1024 and 65535, however the default of 7891 is
recommended.
Enter a custom value or press ENTER to accept default [7891]:
>
>>> Please specify passphrase for Dbvagent
Each Dbvisit Agent must have a passpharse specified. This passphrase
does not have to match between all the servers. It will be used to
establish a secure connection between the GUI (Dbvserver) and the
Dbvisit Agent.
Enter a custom value:
> root
-----------------------------------------------------------
Summary of the Dbvisit DBVAGENT configuration
-----------------------------------------------------------
DBVISIT_BASE /u01/app/dbvisit
DBVAGENT_LOCAL_HOST primaserver
DBVAGENT_LOCAL_PORT 7891
DBVAGENT_PASSPHRASE root
Press ENTER to continue
-----------------------------------------------------------
About to install Dbvisit STANDBY
-----------------------------------------------------------
Component standby installed.
Press ENTER to continue
-----------------------------------------------------------
About to install Dbvisit DBVNET
-----------------------------------------------------------
Component dbvnet installed.
Press ENTER to continue
-----------------------------------------------------------
About to install Dbvisit DBVAGENT
-----------------------------------------------------------
Component dbvagent installed.
Press ENTER to continue
-----------------------------------------------------------
Component Installer Version Installed Version
-----------------------------------------------------------
standby 8.0.04.18184 8.0.04.18184
dbvnet 2.0.04.18184 2.0.04.18184
dbvagent 2.0.04.18184 2.0.04.18184
dbvserver 2.0.04.18184 not installed
-----------------------------------------------------------
What action would you like to perform?
1 - Install component(s)
2 - Uninstall component(s)
3 - Terminate
Your choice: 3
>>> Install log /tmp/dbvisit_install.log.201611180900
[oracle@primaserver installer]$

After software installation, we can now update Dbvisit Standby Configuration Files (DDC). Just note that dbvnet and dbvagent must be started on both servers. dbvctl is used for upgrading DDC file. In our case we have only one DDC file for our instance ORCL.

[oracle@primaserver dbvnet]$ ./dbvnet -d start
[oracle@primaserver dbvagent]$ ./dbvagent -d start


[oracle@primaserver dbvisit8]$ cd /u01/app/dbvisit/standby/
[oracle@primaserver standby]$ pwd
/u01/app/dbvisit/standby
[oracle@primaserver standby]$ ls
conf dbvctl doc gs lib log pid tmp trace
[oracle@primaserver standby]$ ./dbvctl -d ORCL –o upgrade

The last step is to upgrade the central console dbvserver only on the primary server.

[oracle@primaserver installer]$ ./install-dbvisit
-----------------------------------------------------------
Welcome to the Dbvisit software installer.
-----------------------------------------------------------
It is recommended to make a backup of our current Dbvisit software
location (Dbvisit Base location) for rollback purposes.
Installer Directory /home/oracle/dbvisit/dbvisit8/dbvisit
>>> Please specify the Dbvisit installation directory (Dbvisit Base).
The various Dbvisit products and components - such as Dbvisit Standby,
Dbvisit Dbvnet will be installed in the appropriate subdirectories of
this path.
Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
> /u01/app/dbvisit
DBVISIT_BASE = /u01/app/dbvisit
-----------------------------------------------------------
Component Installer Version Installed Version
-----------------------------------------------------------
standby 8.0.04.18184 8.0.04.18184
dbvnet 2.0.04.18184 2.0.04.18184
dbvagent 2.0.04.18184 2.0.04.18184
dbvserver 2.0.04.18184 not installed
-----------------------------------------------------------
What action would you like to perform?
1 - Install component(s)
2 - Uninstall component(s)
3 - Terminate
Your choice: 1
Which component do you want to install?
1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent)
2 - Dbvisit Standby Core (Command Line Interface)
3 - Dbvnet (Dbvisit Network Communication)
4 - Dbvagent (Dbvisit Agent)
5 - Dbvserver (Dbvisit Central Console)
6 - Exit Installer
Your choice: 5
-----------------------------------------------------------
About to configure DBVISIT DBVSERVER
-----------------------------------------------------------
>>> Please specify the host name to be used for Dbvserver
The Dbvisit Web Server (Dbvserver) will be listening on this local
address. If using a cluster or virtual IP make sure the host name or
alias specified here resolve to the IP address local to where Dbvserver
is installed.
If you are unsure about the remote host name during installation, use
the default value which will be the current local hostname.
Enter a custom value or press ENTER to accept default [primaserver]:
>
>>> Please specify the listening port number for Dbvserver on the local server
You may choose any value between 1024 and 65535. The default recommended
value is 4433.
Note: if you can not access this port after the installation has
finished, then please double-check your server firewall settings
to ensure the selected port is open.
Enter a custom value or press ENTER to accept default [4433]:
>
-----------------------------------------------------------
Summary of the Dbvisit DBVSERVER configuration
-----------------------------------------------------------
DBVISIT_BASE /u01/app/dbvisit
DBVSERVER_LOCAL_HOST primaserver
DBVSERVER_LOCAL_PORT 4433
Press ENTER to continue
-----------------------------------------------------------
About to install Dbvisit DBVSERVER
-----------------------------------------------------------
Component dbvserver installed.
Press ENTER to continue
-----------------------------------------------------------
Component Installer Version Installed Version
-----------------------------------------------------------
standby 8.0.04.18184 8.0.04.18184
dbvnet 2.0.04.18184 2.0.04.18184
dbvagent 2.0.04.18184 2.0.04.18184
dbvserver 2.0.04.18184 2.0.04.18184
-----------------------------------------------------------
What action would you like to perform?
1 - Install component(s)
2 - Uninstall component(s)
3 - Terminate
Your choice: 3
>>> Install log /tmp/dbvisit_install.log.201611180956

Our upgrade is now finished, let’s connect to the administration GUI
dbvisit8_1

And after logging we can import our previous configurations by using MANAGE CONFIGURATIONS

dbvisit8_3

Ref : https://dbvisit.atlassian.net/wiki/display/DS8QSG/Upgrade+Dbvisit+Standby

 

Cet article Amazon Web Services: Upgrade to Dbvisit Standby 8 est apparu en premier sur Blog dbi services.

Installing Dbvisit Standby 7 between two AWS Linux Instances

Yann Neuhaus - Sat, 2016-11-19 12:47

Dbvisit is compatible with Amazon Cloud. In this article we are going to talk about installation of Oracle SE2 and Dbvisit Standby 7 between 2 AWS linux instances. We suppose that ssh equivalence is configured for user oracle used for dbvisit installation.
First we have to install oracle software on both servers: primaserver and standserver.
To Install oracle-rdbms-server-12cR1-preinstall.x86_64 package yum can be used to configure the repository

[root@primaserver yum.repos.d]# wget http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol7 -O /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
--2016-11-14 03:52:34-- http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol7
Resolving public-yum.oracle.com (public-yum.oracle.com)... 104.80.89.129, 23.54.8.75
Connecting to public-yum.oracle.com (public-yum.oracle.com)|104.80.89.129|:80...connected.
HTTP request sent, awaiting response... 200 OK
Length: 1011
Saving to: ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle’ 100%[======================================] 1,011 --.-K/s in 0s 2016-11-14 03:52:34 (187 MB/s) - ‘/etc/pki/rpm-gpg/RPM-GPG-KEY-oracle’ saved [1011/1011]


[root@primaserver yum.repos.d]# cd /etc/yum.repos.d/
[root@primaserver yum.repos.d]#
[root@primaserver yum.repos.d]# wget http://public-yum.oracle.com/public-yum-ol7.repo
--2016-11-14 03:53:00-- http://public-yum.oracle.com/public-yum-ol7.repo
Resolving public-yum.oracle.com (public-yum.oracle.com)... 23.54.18.75, 104.80.89.129
Connecting to public-yum.oracle.com (public-yum.oracle.com)|23.54.18.75|:80...
connected. HTTP request sent, awaiting response... 200 OK Length: 5119 (5.0K)
Saving to: ‘public-yum-ol7.repo’
100%[======================================>] 5,119 --.-K/s in 0s
2016-11-14 03:53:00 (478 MB/s) - ‘public-yum-ol7.repo’ saved [5119/5119]


[root@primaserver yum.repos.d]# yum install oracle-rdbms-server-12cR1-preinstall

Then after Oracle installation can be launched. Note a silent method is used. Below an example of the response file I used

[oracle@primaserver response]$ cat db_install.rsp | grep -v ^#
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v12.1.0
oracle.install.option=INSTALL_DB_SWONLY
ORACLE_HOSTNAME=primaserver.us-west-2.compute.internal
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/u01/app/oraInventory
SELECTED_LANGUAGES=en
ORACLE_HOME=/u01/app/oracle/product/12.1.0.2/db_1
ORACLE_BASE=/u01/app/oracle
oracle.install.db.InstallEdition=SE2
oracle.install.db.DBA_GROUP=dba
oracle.install.db.OPER_GROUP=dba
oracle.install.db.BACKUPDBA_GROUP=dba
oracle.install.db.DGDBA_GROUP=dba
oracle.install.db.KMDBA_GROUP=dba
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=true

Launching Oracle Installer

[oracle@primaserver database]$ ./runInstaller -silent -ignoreSysPrereqs -responseFile /home/oracle/db_install.rsp
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 500 MB. Actual 13016 MB Passed
Checking swap space: 0 MB available, 150 MB required. Failed <<<< >>> Ignoring required pre-requisite failures. Continuing...
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2016-11-14_08-26-42AM. Please wait ...[oracle@primaserver database]$ [WARNING] [INS-13014] Target environment does not meet some optional requirements.
CAUSE: Some of the optional prerequisites are not met. See logs for details. /tmp/OraInstall2016-11-14_08-26-42AM/installActions2016-11-14_08-26-42AM.log
ACTION: Identify the list of failed prerequisite checks from the log: /tmp/OraInstall2016-11-14_08-26-42AM/installActions2016-11-14_08-26-42AM.log. Then either from the log file or from installation manual find the appropriate configuration to meet the prerequisites and fix it manually.
You can find the log of this install session at:
/u01/app/oraInventory/logs/installActions2016-11-14_08-26-42AM.log

Once Oracle installed let’s create a database ORCL in the primary server with dbca in a silent method

[oracle@primaserver bin]$./dbca -silent -createDatabase \
-templateName General_Purpose.dbc \
-gdbname ORCL -sid ORCL -responseFile NO_VALUE \
-characterSet AL32UTF8 \
-sysPassword root \
-systemPassword root \
-createAsContainerDatabase false\
-databaseType MULTIPURPOSE \
-automaticMemoryManagement false \
-storageType FS \
-ignorePreReqs
Copying database files
1% complete
3% complete
37% complete
Creating and starting Oracle instance
40% complete
45% complete
50% complete
55% complete
56% complete
60% complete
62% complete
Completing Database Creation
66% complete
70% complete
73% complete
85% complete
96% complete
100% complete
Look at the log file "/u01/app/oracle/cfgtoollogs/dbca/ORCL/ORCL.log" for further details.
[oracle@primaserver bin]$


SQL> select host_name from v$instance;
HOST_NAME
----------------------------------------------------------------
primaserver.us-west-2.compute.internal
SQL>
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
--------- --------------------
ORCL READ WRITE

Now it’s time to install dbvisit standby on both servers. The different steps are unzipping the software and running the installer. Output is truncated. But before don’t forget to edit your Security Groups (see blog ) to allow traffic on the differents involved ports .

[oracle@primaserver dbvisit]$ unzip dbvisit-standby7.0.62-el7.zip
Archive: dbvisit-standby7.0.62-el7.zip
inflating: dbvisit-standby7.0.62-el7.tar
[oracle@primaserver dbvisit]$ ls
dbvisit-standby7.0.62-el7.tar dbvisit-standby7.0.62-el7.zip
[oracle@primaserver dbvisit]$ tar xvf dbvisit-standby7.0.62-el7.tar


[oracle@primaserver installer]$ pwd
/home/oracle/dbvisit/dbvisit/installer
[oracle@primaserver installer]$
[oracle@primaserver installer]$ ./install-dbvisit
-------------------------------------------------------------------------------
Welcome. Your Dbvisit product is going to be installed in a moment.
It will be required by you to enter some configuration parameters
during installation.
-------------------------------------------------------------------------------
It is recommended to make a backup of our current Dbvisit software
location for rollback purposes.
>>> INSTALLATION DIRECTORY
Please specify the Dbvisit main installation directory.
The default directory is "/usr/dbvisit".
Note: the various Dbvisit products and components - such as Standby,
Replicate, Dbvnet, and Dbvserver - will be installed in the appropriate
subdirectories of this path.
Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
> /u01/app/dbvisit
-------------------------------------------------------------------------------
ABOUT TO CONFIGURE: DBVISIT STANDBY
-------------------------------------------------------------------------------
Dbvisit Standby is Dbvisit's disaster recovery software for your
Oracle database.
>>> ORACLE USER NAME
Please specify the Oracle user name on this server.
The default user name is "oracle".
Note: you must be logged in as the Oracle user to run Dbvisit installer.
Custom value or ENTER for default [oracle]:
..........
..........
>>> IMPORTANT - PLEASE NOTE THE FOLLOWING REQUIREMENTS BEFORE CONTINUING:
> The Dbvisit Standby, Dbvnet, and Dbvserver software must be installed
on both the primary and standby servers.
> For network communication between the primary and standby server
via Dbvnet port number 7890 must not be blocked by your firewalls.
> Dbvnet must be up and running on both the primary and standby servers
at all times.
> If you wish to use Dbvserver, the Dbvisit web interface, then please
ensure port 8443 is open on your servers' firewalls, as well.
>>> Thank you for using Dbvisit software!
[oracle@primaserver installer]$

Once dbvisit installed on both node, the graphical administration tool can be lauched using the public DNS.
dbvisit7_1
dbvisit7_2
To configure a standby database we can use the GUI or dbvisit_setup executable

[oracle@primaserver dbvisit]$ cd /u01/app/dbvisit/standby/
[oracle@primaserver standby]$ pwd
/u01/app/dbvisit/standby

The first step of the configuration is to create a new dbvisit database setup. Just launch dbvisit_setup, choose option 1 and follow instructions.

[oracle@primaserver standby]$ ./dbvisit_setup
....
....
....
Options:
1) New Dbvisit Database setup (combines options 2,3,4)
1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
2) New Dbvisit Database configuration (DDC) file setup
3) New Dbvisit Archive Management Module (AMM) setup
4) New Dbvisit Database repository (DDR) setup
5) Manage Dbvisit Database repository (DDR)
6) Update Dbvisit Database configuration (DDC) file
7) Create Standby Database (and template)
8) Synchronize Standby Database
9) Uninstall Dbvisit Database repository (DDR)
E) Exit
=========================================================
Please enter choice : 1

And then after  we can create standby database by running again dbvisit_setup, choose option 7  and follow instructions.

[oracle@primaserver standby]$ ./dbvisit_setup
=========================================================
Dbvisit Standby Database Technology (7.0.62.16992)
....
....
....
Options:
1) New Dbvisit Database setup (combines options 2,3,4)
1a) New Dbvisit RAC Instance setup (combines options 2,3,4)
2) New Dbvisit Database configuration (DDC) file setup
3) New Dbvisit Archive Management Module (AMM) setup
4) New Dbvisit Database repository (DDR) setup
5) Manage Dbvisit Database repository (DDR)
6) Update Dbvisit Database configuration (DDC) file
7) Create Standby Database (and template)
8) Synchronize Standby Database
9) Uninstall Dbvisit Database repository (DDR)
E) Exit
=========================================================
Please enter choice : 7

 

Cet article Installing Dbvisit Standby 7 between two AWS Linux Instances est apparu en premier sur Blog dbi services.

Dynamic Fields

Tom Kyte - Sat, 2016-11-19 10:06
Hi, I am ramesh developing the web application using java and oracle.Our requirment is user can add the fields dynamically for ex: Step 1: user enters name,age we will store that value in parent table. ID COLUMNS_ 1 name ...
Categories: DBA Blogs

ORA-04021: timeout occurred while waiting to lock object on SYS.DBMS_AQADM.CREATE_QUEUE

Tom Kyte - Sat, 2016-11-19 10:06
Hi, i have a problem during SYS.DBMS_AQADM.CREATE_QUEUE. After 15 minutes Oracle writes : ORA-04021: timeout occurred while waiting to lock object ORA-06512: at "SYS.DBMS_AQADM_SYS", line 3647 ORA-06512: at "SYS.DBMS_AQADM", line 130 In ord...
Categories: DBA Blogs

History of User privileges held

Tom Kyte - Sat, 2016-11-19 10:06
In Oracle 12c or 11g, is it possible to fetch the history of user privileges held by a schema? Say from last two months, I might have granted different roles and privileges. I can get the current privileges the schema holds, but is it possible to kno...
Categories: DBA Blogs

Does a Pragma serially_reusable clause is helpful for the .net front end that calls the package.

Tom Kyte - Sat, 2016-11-19 10:06
Does a Pragma serially_reusable clause is helpful for the .net front end that calls the package. I have a package create or replace pkg_test as Pragma serially_reusable l_var number := 0 //some code here end; this package is called by ...
Categories: DBA Blogs

Frequent Truncate

Tom Kyte - Sat, 2016-11-19 10:06
We are frequently truncating partitions in a stage schema through java after loading data into a target table. Once partitions are truncated frequently are there any other steps to be taken to release the space?
Categories: DBA Blogs

Inserts inside before update trigger

Tom Kyte - Sat, 2016-11-19 10:06
I've come across this issue during trigger code testing today. My requirement is, 1. If INSERTING then statements in this block should execute on T1. 2. If UPDATING then statements in this block should execute on T1. It has IF ELSE block and it ...
Categories: DBA Blogs

Query for selecting top 10 percent of records

Tom Kyte - Sat, 2016-11-19 10:06
Hi Tom, I have the requirement of selecting top 10 percent for each group based on score for the below data "GROUPID" "SCORE" "group1" 13 "group1" 12 "group1" 10 "group1" 12 "group2" 12 "group2" 13 "group2" 16 "group2" 20 "group2" 22 ...
Categories: DBA Blogs

Parse CPU to Parse Elapsd has horrible ratio.. but others not too bad?

Tom Kyte - Sat, 2016-11-19 10:06
Tom - this is from running a statspack report. It captures activity over a 3 day period. Instance Efficiency Percentages (Target 100%) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Buffer Nowait %: 100.00 Redo NoWait %: 100...
Categories: DBA Blogs

Columnar Storage

Tom Kyte - Sat, 2016-11-19 10:06
Hi Tom, I recently read an article http://visualstudiomagazine.com/Blogs/Data-Driver/2010/11/SQL-Server-Scan-1-Trillion-Rows-Per-Min.aspx which claims to be revolutionary and unmatched. How does Oracle measure up to it? Very recently new jargons h...
Categories: DBA Blogs

Arrival

Tim Hall - Sat, 2016-11-19 07:29

Imagine someone watched Independence Day and thought, “What a complete sack of shite! I’m going to make something completely the opposite of that!” What you would probably get is Arrival.

It is absolutely not your typical alien action film. It focusses on how we would communicate with visiting aliens who experience everything in a completely different way to us. I can’t really say much more than that or it will ruin things for you.

I really enjoyed it. It’s well worth seeing in my opinion!

Cheers

Tim…

Arrival was first posted on November 19, 2016 at 2:29 pm.
©2012 "The ORACLE-BASE Blog". Use of this feed is for personal non-commercial use only. If you are not reading this article in your feed reader, then the site is guilty of copyright infringement.

Pages

Subscribe to Oracle FAQ aggregator