Skip navigation.

Feed aggregator

Free Formspider Webinar (an APEX Alternative)

Gerger Consulting - Thu, 2014-10-02 04:11
We'd like to invite you to our free Formspider webinar on October 7th. In the webinar, you'll get a chance to find out how Formspider can help you build great web applications with PL/SQL and why we think Formspider is better than APEX.

More importantly, current Formspider customers will join the webinar and talk about their experience with the product.

The webinar is free but space is limited. Sign up now.
Categories: Development

Oracle OEM Cloud Control 12c upgrade to 12.1.0.4

Yann Neuhaus - Thu, 2014-10-02 02:12

In this blog post, I will describe how to upgrade from Oracle Enterprise Manager Cloud Control 12.1.0.3 to OEM 12.1.0.4.0. I have already described the main new features of Cloud Control 12.1.0.4 version in an earlier post (Oracle OEM Cloud Control 12.1.0.4 - the new features). The first pre-requisite is to apply the patch 11061801 on the repository database in 11.2.0.3 version, using the classical opatch apply method. Then, we can begin the upgrade phase.

First, we should explicitly stop the OMS jvmd and adp engines:

 

oracle@vmtestoraem12c:/home/oracle/ [oms12c] emctl extended oms jvmd stop -allOracle Enterprise Manager Cloud Control 12c Release 3Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.Please enter the SYSMAN password:Stopping all Engines{}

No engines found for this operation

oracle@vmtestoraem12c:/home/oracle/ [oms12c] emctl extended oms adp stop -a

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.

No valid registry entry found for verb jv

 

Then we stop the OMS:

 

oracle@vmtestoraem12c:/home/oracle/ [oms12c] emctl stop oms -all

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.

All rights reserved.Stopping WebTier...

WebTier Successfully Stopped

Stopping Oracle Management Server...

Oracle Management Server Successfully Stopped

AdminServer Successfully Stopped

Oracle Management Server is Down

 

We stop the management agent:

 

oracle@vmtestoraem12c:/home/oracle/ [agent12c] emctl stop agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.

All rights reserved.

Stopping agent ..... stopped.


Finally after unzipping the 12.1.0.4 binary files, we can run the installer:

 

cc1

 

We choose not to receive security updates:

 

cc2

cc3

 

 

We choose to skip the updates:

 

cc4

 

All the prerequisites checks have succeeded :=)

 

cc5

 

We select a One System Upgrade and the Oracle_Home where the 12.1.0.3 version is installed:

 

cc7

 

We select the new Middleware Home:

 

cc8

 

We enter the administration passwords:

 

cc9

 

The installer reminds you that you have correctly patched the repository database. Let's check if it is correct:

 

Interim patches (1) :

Patch 11061801 : applied on Mon Aug 04 16:52:51 CEST 2014

Unique Patch ID: 16493357

Created on 24 Jun 2013, 23:28:20 hrs PST8PDT

Bugs fixed: 11061801

 

cc10

 

We did not copy the emkey to the repository, so we have to run:

 

oracle@vmtestoraem12c:/u01/app/oracle/MiddleWare_12103/oms/bin/ [oms12c] emctl config emkey -copy_to_repos_from_file -repos_conndesc '"(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=vmtestoraem12c.it.dbi-services.com)(PORT=1521)))(CONNECT_DATA=(SID=OMSREP)))"' -repos_user sysman -emkey_file /u01/app/oracle/MiddleWare_12103/oms/sysman/config/emkey.ora

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.

All rights reserved.

Enter Admin User's Password :

Enter Enterprise Manager Root (SYSMAN) Password :

The EMKey has been copied to the Management Repository.

This operation will cause the EMKey to become unsecure.

 

After the required operation has been completed, secure the EMKey by running "emctl config emkey -remove_from_repos":

 

cc11

 

We select Yes to let the installer fix the isssue automatically:

 

cc12

 

We select Next:

 

cc13

 

We can select additionnal plugins:

 

cc14

 

We enter the weblogic password:

 

cc15

 

We select install:

 

cc16

 

And finally we run the allroot.sh script connected as root:

 

cc17

 

The upgrade is successfull! Let's check the OMs status:

 

oracle@vmtestoraem12c:/u01/app/oracle/MiddleWare_12cR4/oms/ [oms12c] emctl status oms -details

Oracle Enterprise Manager Cloud Control 12c Release 4

Copyright (c) 1996, 2014 Oracle Corporation.

All rights reserved.

Enter Enterprise Manager Root (SYSMAN) Password :

Console Server Host : vmtestoraem12c.it.dbi-services.com

HTTP Console Port : 7789

HTTPS Console Port : 7801

HTTP Upload Port : 4890

HTTPS Upload Port : 4901

EM Instance Home : /u01/app/oracle/gc_inst/em/EMGC_OMS1

OMS Log Directory Location : /u01/app/oracle/gc_inst/em/EMGC_OMS1/sysman/log

OMS is not configured with SLB or virtual hostname

Agent Upload is locked.

OMS Console is locked.

Active CA ID: 1

Console URL: https://vmtestoraem12c.it.dbi-services.com:7801/em

Upload URL: https://vmtestoraem12c.it.dbi-services.com:4901/empbs/upload

WLS Domain InformationDomain Name : GCDomain

Admin Server Host : vmtestoraem12c.it.dbi-services.com

Admin Server HTTPS Port: 7102

Admin Server is RUNNING

Oracle Management Server Information

Managed Server Instance Name: EMGC_OMS1

Oracle Management Server Instance Host: vmtestoraem12c.it.dbi-services.com

WebTier is Up

Oracle Management Server is Up

BI Publisher is not configured to run on this host.

 

Now we have access to the Enterprise Manager Cloud Control 12.1.0.4:

 

cc18

 

The next step consists in upgrading the management agents. From the Setup menu, we select Upgrade Agents:

 

cc19

cc20

 

The management agent is detected:

 

cc21

 

The operation is successfull:

 

cc22

 

The update to 12.1.0.4 Enterprise Manager version did not cause any problem and has a new feature which checks the correct patching of the Enterprise Manager repository database.

Run #em12c on #db12c? – Discussion from Oracle Open World (MOS Note: 1920632.1)

DBASolved - Wed, 2014-10-01 13:38

Ok Folks, I’ve been here are Oracle Open World for a few days now.  In that time, I’ve had numerous conversations about running Oracle Enterprise Manager 12c on Oracle Database 12c.  I will be honest and say that I’ve enjoyed these conversations; however, after about the fourth time I decided I need to write a quick post on the explanation discussed in these conversations.  

Early this year (August) I wrote a post about the what came out of the OEM CAB in May 2014 and how to get OEM 12c to work on DB12c.  The concept of running OEM 12c on DB12c, pluggable or not, have many people excited and looking forward to configuring OEM to do that very configuration.  Heck, I’ve even installed it for a few customers in that configuration (non-PDB).  So I’m a bit sad in having to say this:  ORACLE DATABASE 12c SUPPORT FOR THE REPOSITORY DATABASE IS TEMPORARILY SUSPENDED!  I say this due to the My Oracle Support (MOS) Note: 1920632.1.

Note 1920632.1 states the following:

Due to some recently discovered scenarios, we (Oracle) are temporarily suspending the certification of DB 12.1.0.1 and DB 12.1.0.2 as a Certified Repository version for EM 12c R4 until additional testing is complete.

Now what does this mean for those customers and clients that have already built their OEM 12c repository on DB 12c (12.1.0.1 or 12.1.0.2)?  The MOS note outlines what to do in the action section of the note:

Until testing is complete on the 12c Database, Oracle recommends using DB 11.2.0.4 as the EM 12c R4 Repository. 

If you are currently running a 12c DB repository, please be aware that additional testing is underway and there are currently no bugs or patches required; but if testing proves a patch is required, we will update this announcement.  You do not need to deinstall EM 12c or move the repository to an 11.2.0.4 database.

Sure hope Oracle quickly finishes testing and can restore support for DB 12c as the OEM repository.  In the meantime, everyone should know about this note number and be aware when making architecture changes related to their OEM 12c environment.

Enjoy!

about.me: http://about.me/dbasolved


Filed under: OEM
Categories: DBA Blogs

OCP 12C – In Database Archiving and Temporal Validity

DBA Scripts and Articles - Wed, 2014-10-01 13:14

In Database Archiving In Database Archiving is a new feature of Oracle 12c meant to solve management of historical data inside the database. Like its name says, this functionnality leaves data into the database, so it remains accessible if you need it. With In Database Archiving, historical data remains in the database but is invisible to [...]

The post OCP 12C – In Database Archiving and Temporal Validity appeared first on Oracle DBA Scripts and Articles (Montreal).

Categories: DBA Blogs

OOW14 Day 3 - 12c Adaptive Bitmap Pruning

Yann Neuhaus - Wed, 2014-10-01 13:10

I'm currently following the session 'Real-World Performance of Star and Snowflake Schemas' with Michael Hallas, Andrew Holdsworth, John Clarke. It's really a good presentation. the Real Performance team tries to spread messages about how to design for performance. But today I'll not blog about what I've seen but about what I've not seen. Everybody talks about those nice 12c features that are useful in BI workloads, such as adaptive joins, adaptive parallel distribution, vector 'in-memory' aggregation, etc. Nobody talks about Adaptive Bitmap Pruning.

If you google for for it there is only one result (at least before my blog is published) which is the patent about all all those new CBO features that came in 12.1.0.1

And when I assist to a session that shows star transformation and execution plans with and without temporary table, I'm frustrated that I don't see anything about that great feature that stabilizes our BI reports on star schemas. I'm preparing our tuning workshop (dates here - 10% discount if you book before the end of the year) and it's something I can't skip when talking about star transformation and bitmap indexes.

So let's have a look to it. It you want a refresh about star transformation, please just wait about the next SOUG newsletter. But if you're already familiar with it, this is for you.

Let's have a look at an execution plan in 12c after running a query on a star schema. You have the same as in 11g except that we have that grayed ‘STATISTICS COLLECTOR’. Star transformation is good when the predicate is selective enough to filter few rows. Imagine that the cardinality estimation was wrong and most of FACT rows have the required value. This is what happened here, and the optimizer has chosen to stop iterating in that bitmap branch. It just ignores the predicate at that step and the join back to the dimension Cartesian join will filter it anyway.

If you check the execution plan with predicates you will see the predicate on dimension in the two table access.

12cAdaptiveBitmapPruning.png

Look at the end. When the statistics collector has seen that the threshold has been passed over, it has decided to skip that bitmap branch. This is Adaptive Bitmap Pruning. The bitmap branch is good only if it helps to filter a lot of rows. If it’s not the case, then it’s just an overhead and it is skipped, coming back - for that branch only - to the behavior we have when star transformation was disabled.

As with the other adaptive plans, the threshold is calculated at parse time.

See more details about the inflection point in a previous blog about Adaptive Joins

 

OCP 12C – Information Lifecycle Management and Storage Enhancements

DBA Scripts and Articles - Wed, 2014-10-01 10:16

Information Lifecycle Management Before reading this flashcard I recommend you to read my article on ILM. Automatic Data Optimization (ADO) Policy based data management Let you define policies at : Tablespace level Segment level Row level Policies can either compress data or move data to a different tablespace Policies let you define when, what and [...]

The post OCP 12C – Information Lifecycle Management and Storage Enhancements appeared first on Oracle DBA Scripts and Articles (Montreal).

Categories: DBA Blogs

Join me in a FREE live webcast about Real-Time Query!

The Oracle Instructor - Wed, 2014-10-01 08:50

On Thursday, 2nd October, 12:30 CET I will be doing a Live Webcast with many demonstrations about Data Guard Real-Time Query.

The shown features all work with 11g already.

Register here.

805-banner-dataguardrealtime-v1-2294812Addendum: The webcast was done already.


Tagged: Active Data Guard, Data Guard, OU Streams
Categories: DBA Blogs

Oracle APEX 5 Update from OOW

Scott Spendolini - Wed, 2014-10-01 08:18
The big news about Oracle APEX from OOW is not so much about what, but more about when.  Much to many people's disappointment, APEX 5.0 is still going to be a few months out.  The "official" release date has been updated from "calendar year 2014" to "fiscal year 2015".  For those not in the know, Oracle's fiscal year ends on May 31st, so that date represents the new high-water mark.

Despite this bit of bad news, there were a number of bits of good news as well.  First of all, there will be an EA3.  This is good because it demonstrates that the team has been hard at work fixing bugs and adding features.  Based on the live demonstrations that were presented, there are some subtle and some not-so-subtle things to look forward to.  The subtle include an even more refined UI, complete with smooth fade-through transitions.  I tweeted about the not-so-subtle the other day, but to recap here: pivot functionality in IRs, column toggle and reflow in jQuery Mobile.

After (or right before - it wasn't 100% clear) that E3 is released, the Oracle APEX team will host their first public beta program.  This will enable select customers to download and install APEX 5.0 on their own hardware.  This is an extraordinary and much-needed positive change in their release cycle, as for the first time, customers can upgrade their actual applications in their environment and see what implications APEX 5.0 will bring.  Doing a real-world upgrade on actual APEX applications is something that the EA instances could never even come close to pulling of.

After the public beta, Oracle will upgrade their internal systems to APEX 5.0 - and there's a lot of those.  At last count, I think the number of workspaces was just north of 3,000.  After the internal upgrade, apex.oracle.com will have it's turn.  And once that is complete, we can expect APEX 5.0 to be released.

No one like delays.  But in this case, it seems that the extra time required is quite justified, as APEX 5.0 still needs some work, and the upgrade path from 4.x needs to be nothing short of rock-solid.  Keep in mind that with each release, there are a larger number of customers using a larger number of applications, so ensuring that their upgrade experience is as smooth as possible is just as, if not more important than any new functionality.

In the mean time, keep kicking the tires on the EA instance and provide any feedback or bug reports!

Shrink Tablespace

Jonathan Lewis - Wed, 2014-10-01 07:55

In a comment on my previous post on shrinking tablespaces Jason Bucata and Karsten Spang both reported problems with small objects that didn’t move to the start of the tablespace. This behaviour is inevitable with dictionary managed tablespaces (regardless of the size of the object), but I don’t think it’s likely to happen with locally managed tablespaces if they’ve been defined with uniform extent sizes. Jason’s comment made me realise, though, that I’d overlooked a feature of system allocated tablespaces that made it much harder to move objects towards the start of file. I’ve created a little demo to illustrate the point.

I created a new tablespace as locally managed, ASSM, and auto-allocate, then created a few tables or various sizes. The following minimal SQL query reports the resulting extents in block_id order, adding in a “boundary_1m” column which subtracts 128 blocks (1MB) from the block_id, then divides by 128 and truncates to show which “User Megabyte” in the file the extent starts in.  (Older versions of Oracle typically have an 8 block space management header, recent versions expanded this from 64KB to 1MB – possibly as a little performance aid to Exadata).


select
        segment_name, block_id, blocks , trunc((block_id - 128)/128) boundary_1M
from
        dba_extents where owner = 'TEST_USER'
order by
        block_id
;

SEGMENT_NAME               BLOCK_ID     BLOCKS BOUNDARY_1M
------------------------ ---------- ---------- -----------
T1                              128       1024           0
T1                             1152       1024           8
T2                             2176       1024          16
T2                             3200       1024          24
T3                             4224          8          32
T4                             4232          8          32
T5                             4352        128          33

As you can see t3 and t4 are small tables – 1 extent of 64KB each – and t5, which I created after t4, starts on the next 1MB boundary. This is a feature of auto-allocate: not only are extents (nearly) fixed to a small number of possible extent sizes, the larger extents are restricted to starting on 1MB boundaries and the 64KB extents are used preferentially to fill in odd-sized” holes. To show the impact of this I’m going to drop table t1 (at the start of file) to make some space.


SEGMENT_NAME               BLOCK_ID     BLOCKS BOUNDARY_1M
------------------------ ---------- ---------- -----------
T2                             2176       1024          16
T2                             3200       1024          24
T3                             4224          8          32
T4                             4232          8          32
T5                             4352        128          33

Now I’ll move table t3 – hoping that it will move to the start of file and use up some of the space left by t1. However there’s a 1MB area (at boundary 32) which is partially used,  so t3 moves into that space rather than creating a new “partly used” megabyte.


SEGMENT_NAME               BLOCK_ID     BLOCKS BOUNDARY_1M
------------------------ ---------- ---------- -----------
T2                             2176       1024          16
T2                             3200       1024          24
T4                             4232          8          32
T3                             4240          8          32
T5                             4352        128          33

It’s a little messy trying to clear up the tiny fragments and make them do what you want. In this case you could, for example, create a dummy table with storage(initial 64K next 64K minextents 14) to use up all the space in the partly used megabyte, then move t3 – which should go to the start of file – then move table t4 – which should go into the first partly-used MB (i.e. start of file) rather than taking up the hole left by t3.

Even for a trivial example it’s messy – imagine how difficult it can get to cycle through building and dropping suitable dummy tables and move objects in the right order when you’ve got objects with several small extents scattered through the file, and objects with a mixture of small extents and large extents.


OCP 12C – Backup, Recovery and Flashback for a CDB/PDB

DBA Scripts and Articles - Wed, 2014-10-01 07:43

Backup a CDB/PDB To make a database backup you need the SYSBACKUP or SYSDBA privilege. You can backup the CDB and all the PDBs independantly, all together, or by specifying a list. You can backup a PDB by connecting directly to it and use: RMAN> BACKUP DATABASE: You can backup a PDB by connecting to [...]

The post OCP 12C – Backup, Recovery and Flashback for a CDB/PDB appeared first on Oracle DBA Scripts and Articles (Montreal).

Categories: DBA Blogs

Solving customer issues at OOW14: Dbvisit Replicate can replicate tables without primary key

Yann Neuhaus - Wed, 2014-10-01 06:39

Usually, the logical replication of changes uses the primary key. Each row updated or deleted generate a statement to be applied on the target, which affects only one row because it accesses with the primary key. If there is no primary key, we need to have something unique and at worst it is the whole row. But sometimes old applications were designed before being implemented into relational database and have no unicity. It it a problem for logical replication? We will see that Dbvisit replicate can address that.

Here is the case I encountered at a customer. The application has a master-detail table design, and the detail tables are inserted/deleted all together for the same master key. And there is no primary key, and even nothing unique. The only value that may help is a timestamp but sometimes timestamps do not have the sufficient precision to be unique. And anyway, imagine what happens if we change back the system time, or during daylight saving changes.

At dbi services we have very good contact with our partner Dbvisit and it's the kind of question that can be addressed quickly by the support. Anyway, I was at the Oracle Open World and then was able to discuss directly with the Dbvisit replicate developers. There is a solution and it is even documented.

The basic issue is that when the delete occurs, a redo entry is generated for each row that is deleted and then Dbvisit replicate generates an update statement to do the same on the target. But when there are duplicates the first statement will affect several rows and the next statement will affect no rows.

This is the kind of replication complexity that is addressed with conflict resolution. It can be addressed manually: the replication stops when a conflict is detected and continues once we have decided what to do. But we can also set rules to address it automatically when the problem occurs again so that the replication never stops.

Here is the demo about that as I tested it before providing the solution to my customer. 

Note that it concerns only deletes here but the same can be done with updates.

1. I create a table with 4 identical rows for each value of N:

  create table TESTNOPK as select n,'x' x from (select rownum n from dual connect by level
SQL> connect repoe/repoe Connected.
SQL> create table TESTNOPK as select n,'x' x from (select rownum n from dual connect by level   Table created.

2. Status of replication from the Dbvisit console:


| Dbvisit Replicate 2.7.06.4485(MAX edition) - Evaluation License expires in 29 days MINE IS running. Currently at plog 35 and SCN 796568 (10/01/2014 01:08:04). APPLY IS running. Currently at plog 35 and SCN 796566 (10/01/2014 01:08:04). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:40/40           Unrecov:0/0         Applied:40/40       Conflicts:0/0       Last:01/10/2014 01:08:02/OK -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.  

3. I delete the lines with the value 10:


SQL> select * from TESTNOPK where n=10;
         N X ---------- -         10 x         10 x         10 x         10 x
SQL> delete from TESTNOPK where n=10;
4 rows deleted.
SQL> commit;
Commit complete.

5. apply is stop on a conflict: too many rows affected by the delete


MINE IS running. Currently at plog 35 and SCN 797519 (10/01/2014 01:10:56). APPLY IS running. Currently at plog 35 and SCN 796928 (10/01/2014 01:09:08) and 1 apply conflicts so far (last at 01/10/2014 01:10:57) and WAITING on manual resolve of apply conflict id 35010009996. Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:                90%  Mine:44/44           Unrecov:0/0         Applied:40/40       Conflicts:1/1       Last:01/10/2014 01:09:17/RETRY:Command affected 4 row(s). -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.     dbvrep> list conflict Information for conflict 35010009996 (current conflict): Table: REPOE.TESTNOPK at transaction 0008.003.0000022b at SCN 796930 SQL text (with replaced bind values): delete from "REPOE"."TESTNOPK" where (1=1) and "N" = 10 and "X" = 'x'
Error: Command affected 4 row(s). Handled as: PAUSE Conflict repeated 22 times.

6. I resolve the conflict manually, forcing the delete of all rows

                                                                                                                                                       dbvrep> resolve conflict 35010009996 as force Conflict resolution set.   At that point, there is 3 following conflicts that I need to force as well because of the other deletes affecting no rows. I don't reproduce them here.

7. Once the conflits are resolved, the replication continues:

  MINE IS running. Currently at plog 35 and SCN 800189 (10/01/2014 01:19:16). APPLY IS running. Currently at plog 35 and SCN 800172 (10/01/2014 01:19:14). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:44/44           Unrecov:0/0         Applied:44/44       Conflicts:4/4       Last:01/10/2014 01:18:21/RETRY:Command affected 0 row(s). -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.                                                                                                                                                           dbvrep> list conflict Information for conflict 0 (current conflict): No conflict with id 0 found.  

8. Now I want to set a rule that manages that situation automatically. I add a 'too many rows' conflict rule to touch only one line for each delete:


dbvrep> SET_CONFLICT_HANDLERS FOR TABLE REPOE.TESTNOPK FOR DELETE ON TOO_MANY TO SQL s/$/ and rownum = 1/ Connecting to running apply: [The table called REPOE.TESTNOPK on source is handled on apply (APPLY) as follows: UPDATE (error): handler: RETRY logging: LOG UPDATE (no_data): handler: RETRY logging: LOG UPDATE (too_many): handler: RETRY logging: LOG DELETE (error): handler: RETRY logging: LOG DELETE (no_data): handler: RETRY logging: LOG DELETE (too_many): handler: SQL logging: LOG, regular expression: s/$/ and rownum = 1/ INSERT (error): handler: RETRY logging: LOG TRANSACTION (error): handler: RETRY logging: LOG]                                                                                                                                                        9. Now testing the automatic conflict resolution:   SQL> delete from TESTNOPK where n=9;
4 rows deleted.
SQL> commit;
Commit complete.
10.  the conflicts are automatically managed:   MINE IS running. Currently at plog 35 and SCN 800475 (10/01/2014 01:20:08). APPLY IS running. Currently at plog 35 and SCN 800473 (10/01/2014 01:20:08). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:48/48           Unrecov:0/0         Applied:48/48       Conflicts:7/7       Last:01/10/2014 01:19:57/OK -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.  

Now the replication is automatic and the situation is correctly managed.


 oow-imattending-200x200-2225057.gif  

As I already said, Dbvisit is a simple tool but is nethertheless very powerfull. And Oracle Open World is an efficient way to learn: share knowlege during the day, and test it during the night when you are too jetlagged to sleep...





 



 

 

solving customer issue at OOW14: Dbvisit replicate can even replicate tables with no primary key

Yann Neuhaus - Wed, 2014-10-01 06:39
Usually, the logical replication of changes uses the primary key. Each row updated or deleted generate a statement to be applied on the target, which affects only one row because it accesses with the primary key. If there is no primary key, we need to have something unique and at worst it is the whole row. But sometimes old applications were designed before being implemented into relational database and have no unicity. It it a problem for logical replication? We will see that Dbvisit replicate can address that.   Here is the case I encountered at a customer. The application has a master-detail table design, and the detail tables are inserted/deleted all together for the same master key. And there is no primary key, and even nothing unique. The only value that may help is a timestamp but sometimes timestamps do not have the sufficient precision to be unique. And anyway, imagine what happens if we change back the system time, or during daylight saving changes.   At dbi services we have very good contact with our partner Dbvisit and it's the kind of question that can be addressed quickly by the support. Anyway, I was at the Oracle Open World and then was able to discuss directly with the Dbvisit replicate developers. There is a solution and it is even documented.

The basic issue is that when the delete occurs, a redo entry is generated for each row that is deleted and then Dbvisit replicate generates an update statement to do the same on the target. But when there are duplicates the first statement will affect several rows and the next statement will affect no rows.

This is the kind of replication complexity that is addressed with conflict resolution. It can be addressed manually: the replication stops when a conflict is detected and continues once we have decided what to do. But we can also set rules to address it automatically when the problem occurs again so that the replication never stops.

Here is the demo about that as I tested it before providing the solution to my customer. 

Note that it concerns only deletes here but the same can be done with updates.

1. I create a table with 4 identical rows for each value of N:

  create table TESTNOPK as select n,'x' x from (select rownum n from dual connect by level
SQL> connect repoe/repoe Connected.
SQL> create table TESTNOPK as select n,'x' x from (select rownum n from dual connect by level   Table created.

2. Status of replication from the Dbvisit console:


| Dbvisit Replicate 2.7.06.4485(MAX edition) - Evaluation License expires in 29 days MINE IS running. Currently at plog 35 and SCN 796568 (10/01/2014 01:08:04). APPLY IS running. Currently at plog 35 and SCN 796566 (10/01/2014 01:08:04). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:40/40           Unrecov:0/0         Applied:40/40       Conflicts:0/0       Last:01/10/2014 01:08:02/OK -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.  

3. I delete the lines with the value 10:


SQL> select * from TESTNOPK where n=10;
         N X ---------- -         10 x         10 x         10 x         10 x
SQL> delete from TESTNOPK where n=10;
4 rows deleted.
SQL> commit;
Commit complete.

5. apply is stop on a conflict: too many rows affected by the delete


MINE IS running. Currently at plog 35 and SCN 797519 (10/01/2014 01:10:56). APPLY IS running. Currently at plog 35 and SCN 796928 (10/01/2014 01:09:08) and 1 apply conflicts so far (last at 01/10/2014 01:10:57) and WAITING on manual resolve of apply conflict id 35010009996. Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:                90%  Mine:44/44           Unrecov:0/0         Applied:40/40       Conflicts:1/1       Last:01/10/2014 01:09:17/RETRY:Command affected 4 row(s). -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.     dbvrep> list conflict Information for conflict 35010009996 (current conflict): Table: REPOE.TESTNOPK at transaction 0008.003.0000022b at SCN 796930 SQL text (with replaced bind values): delete from "REPOE"."TESTNOPK" where (1=1) and "N" = 10 and "X" = 'x'
Error: Command affected 4 row(s). Handled as: PAUSE Conflict repeated 22 times.

6. I resolve the conflict manually, forcing the delete of all rows

                                                                                                                                                       dbvrep> resolve conflict 35010009996 as force Conflict resolution set.   At that point, there is 3 following conflicts that I need to force as well because of the other deletes affecting no rows. I don't reproduce them here.

7. Once the conflits are resolved, the replication continues:

  MINE IS running. Currently at plog 35 and SCN 800189 (10/01/2014 01:19:16). APPLY IS running. Currently at plog 35 and SCN 800172 (10/01/2014 01:19:14). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:44/44           Unrecov:0/0         Applied:44/44       Conflicts:4/4       Last:01/10/2014 01:18:21/RETRY:Command affected 0 row(s). -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.                                                                                                                                                           dbvrep> list conflict Information for conflict 0 (current conflict): No conflict with id 0 found.  

8. Now I want to set a rule that manages that situation automatically. I add a 'too many rows' conflict rule to touch only one line for each delete:


dbvrep> SET_CONFLICT_HANDLERS FOR TABLE REPOE.TESTNOPK FOR DELETE ON TOO_MANY TO SQL s/$/ and rownum = 1/ Connecting to running apply: [The table called REPOE.TESTNOPK on source is handled on apply (APPLY) as follows: UPDATE (error): handler: RETRY logging: LOG UPDATE (no_data): handler: RETRY logging: LOG UPDATE (too_many): handler: RETRY logging: LOG DELETE (error): handler: RETRY logging: LOG DELETE (no_data): handler: RETRY logging: LOG DELETE (too_many): handler: SQL logging: LOG, regular expression: s/$/ and rownum = 1/ INSERT (error): handler: RETRY logging: LOG TRANSACTION (error): handler: RETRY logging: LOG]                                                                                                                                                        9. Now testing the automatic conflict resolution:   SQL> delete from TESTNOPK where n=9;
4 rows deleted.
SQL> commit;
Commit complete.
10.  the conflicts are automatically managed:   MINE IS running. Currently at plog 35 and SCN 800475 (10/01/2014 01:20:08). APPLY IS running. Currently at plog 35 and SCN 800473 (10/01/2014 01:20:08). Progress of replication dbvrep_XE:MINE->APPLY: total/this execution -------------------------------------------------------------------------------------------------------------------------------------------- REPOE.CUSTOMERS:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ADDRESSES:              100%  Mine:1864/1864       Unrecov:0/0         Applied:1864/1864   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.CARD_DETAILS:           100%  Mine:1727/1727       Unrecov:0/0         Applied:1727/1727   Conflicts:0/0       Last:30/09/2014 02:38:30/OK REPOE.ORDER_ITEMS:            100%  Mine:12520/12520     Unrecov:0/0         Applied:12520/12520 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.ORDERS:                 100%  Mine:10040/10040     Unrecov:0/0         Applied:10040/10040 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.INVENTORIES:            100%  Mine:12269/12269     Unrecov:0/0         Applied:12269/12269 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.LOGON:                  100%  Mine:12831/12831     Unrecov:0/0         Applied:12831/12831 Conflicts:0/0       Last:30/09/2014 02:38:35/OK REPOE.TESTNOPK:               100%  Mine:48/48           Unrecov:0/0         Applied:48/48       Conflicts:7/7       Last:01/10/2014 01:19:57/OK -------------------------------------------------------------------------------------------------------------------------------------------- 8 tables listed.  

Now the replication is automatic and the situation is correctly managed.


 oow-imattending-200x200-2225057.gif  

As I already said, Dbvisit is a simple tool but is nethertheless very powerfull. And Oracle Open World is an efficient way to learn: share knowlege during the day, and test it during the night when you are too jetlagged to sleep...





 



 

 

Oracle #GoldenGate Parameter File Templates

DBASolved - Wed, 2014-10-01 01:27

This week I’ve been enjoying spending some time at Oracle Open World in San Francisco, CA.  While here, I’ve been talking with everyone, friends old and new, and it came to my attention that it would be a good idea to have some useful templates for Oracle GoldenGate parameter files.  With this in mind, I decided to create some generic templates with comments for Oracle GoldenGate processes.  These templates can be found on my Scripts page under “Oracle GoldenGate Parameter Templates”.  These files are in a small zip file that can be downloaded, unzipped and used in creating a basic uni-directional configuration.

By using these templates, you should be able to do:

  1. Review useful examples for each Oracle GoldenGate process (Manager, Extract, Pump, Replicat)
  2. With minor changes, quickly get uni-directional replication going
  3. Gain a base understanding of what how simple Oracle GoldenGate parameter files work

Enjoy!

about.me: http://about.me/dbasolved

 


Filed under: Golden Gate
Categories: DBA Blogs

2016 Mazda6 Interior Review

Ameed Taylor - Wed, 2014-10-01 01:15
If there's an ethical to the absolutely redesigned 2016 Mazda6 Interior Review  story, it's that there may be extra to lifestyles than "zoom-zoom." The previous-generation Mazda 6 had a whole lot of it, yet Mazda had a satan of a time getting the shopping for public to notice. which is as a result of American drivers usually do not care a lot about how their domestic sedans behave on winding united states of america roads. What they want is space, security, reliability, energy and magnificence -- and while the outdated 6 looked nice sufficient, its tight dimensions and lackluster acceleration averted it from succeeding in an increasingly more competitive marketplace.

the new 6 demonstrates that Mazda wasn't going to make the identical mistake twice. want room to chill out? It bargains one of the vital accommodating cabins of any midsize sedan, with Texas-sized front seats and a backseat match for 6-footers. acquired baggage, or in all probability 4 units of golf golf equipment? The midsize Mazda now options an impressively massive 16.6 cubic toes of trunk space. need energy? Mazda's received you covered with the biggest and strongest V6 on this worth bracket, though its gasoline financial system is disappointing. need to make a way commentary? then you definately shouldn't be shopping for a family sedan within the first position. but as such cars go, we think the brand new 6 manages to be tautly horny, in particular from the front, despite its additional 6.1 inches of length and 2.three inches of width. in contrast to the previous model, the 2016 Mazda6 Interior Review  used to be engineered namely for the North American market -- and it shows.

It additionally method introduced weight, as the enlarged 6 is roughly a hundred and fifty pounds heavier than its predecessor. yet you can nonetheless discover the sporty reflexes that consumers have come to expect from this efficiency-oriented brand. physique roll is minimal through domestic-sedan requirements, and the steerage is light however responsive. The 6 by no means allows you to omit its really extensive dimension, but its smartly-sorted chassis and light-on-its-ft character at pace places it 2nd most effective to the Nissan Altima within the fun-to-force category.

Wait a minute, you might be announcing -- how might the "zoom-zoom" household sedan fail to be the sportiest automobile in its class? Three causes: The Altima's significantly lighter, its physique motions are higher managed and its steering is tighter and more communicative. however so what? because the previous 6 validated (and the Toyota Camry continues to reveal), prime-notch riding dynamics don't a very best-promoting household sedan make. What the brand new 6 offers is the coveted combination of american-fashion measurement and energy, along with above-average handling for individuals who care about that kind of thing. authentic fans won't in finding the 6 to their liking -- however hiya, that is what the Mazdaspeed three is for.

in short, the 2009 Mazda 6 is at or close to the top of its class in most respects. As universal, although, we suggest check-riding as many rival models as conceivable earlier than making your resolution, including the Chevrolet Malibu, Honda Accord, Hyundai Sonata, Nissan Altima, Subaru Legacy and Toyota Camry. each has its own strengths and weaknesses, but few can suit the 6's all-round competence and attraction.
battery for mazda 6 key fob
The 2009 Mazda 6 is a entrance-wheel-pressure midsize sedan. There are seven trim ranges: i SV, i activity, i journeying, i Grand visiting, s recreation, s journeying and s Grand visiting. fashions with the i prefix include the 4-cylinder engine, whereas fashions with the s prefix come with the V6.

the worth leader i SV comes usual with sixteen-inch metal wheels, a manually top-adjustable driver seat, full power accessories, a six-speaker CD stereo machine with guidance-wheel-installed audio controls, air-conditioning and a tilt/telescoping steerage column. The i recreation adds cruise keep an eye on, an auxiliary enter jack and keyless entry. The i traveling edition steps up the function content material with 17-inch alloy wheels, foglights, a commute pc, a power driver seat, keyless ignition/entry, electroluminescent gauges, black patterned accent pieces and a leather-based-wrapped steerage wheel and shift knob. The i Grand travelling model provides xenon headlights, heated leather seats with a reminiscence perform for the driving force seat, Bluetooth connectivity, twin-zone automatic climate regulate, auto-dimming mirrors and an auditory blind-spot monitoring device.

The s fashions feature the corresponding i models' usual gear together with just a few enhancements -- the s sport comes with 17-inch alloy wheels and dual exhaust retailers, and the s traveling and s Grand travelling add 18-inch alloy wheels.

A comfort package for visiting models tacks on most of the Grand visiting's standard luxuries, while the Moonroof and Bose bundle adds a sunroof and an upgraded audio system to journeying and Grand journeying fashions. A navigation system is to be had most effective on the Grand journeying. other choices include faraway start, an in-sprint six-CD changer and satellite tv for pc radio.
mazda 6 check engine light
The front-wheel-pressure 2009 Mazda 6 is powered through either a 2.5-liter 4-cylinder engine or a three.7-liter V6. The 4 generates 170 horsepower and 167 pound-feet of torque, while the V6 pumps out 272 hp and 269 lb-ft. A six-velocity manual transmission is standard on 4-cylinder fashions, with a five-velocity automated non-compulsory on all however the i SV. A six-velocity computerized is necessary on V6-powered models.

gasoline-economy estimates stand at 20 mpg metropolis/29 freeway and 23 mixed for 4-cylinder fashions with the manual transmission, while the five-speed auto improves the 4's numbers to 21 mpg metropolis/30 freeway and 24 blended. These are classification-competitive numbers. however, if you go for the V6, estimates drop to 17 mpg city/25 freeway and 20 mixed, which is ready as bad because it gets on this phase.
common problems with mazda 6
Antilock disc brakes, balance control, front-seat facet airbags and entire-length facet curtain airbags are all same old on the aftermarket mazda 6 parts.
difference between mazda 3 and mazda 6
The mazda 6 bluetooth issues control structure is in most cases intuitive, with all major knobs and buttons naturally labeled and simply manipulated. it's sexy, too, with crimson backlighting for the gauges and a swish middle stack sweeping ahead towards the windshield, despite the fact that the atypical black-and-silver patterned plastic trim in journeying models and above is not going to strike everyone's fancy. materials high quality is hit-or-pass over, as the wealthy-feeling soft-contact subject material on the passenger side of the dashboard contrasts with low-cost arduous stuff on the driving force aspect. The emergency brake additionally feels a bit chintzy for this value point. The generously proportioned seats are somewhat at ease, then again, with abundant leg- and headroom all around. On the downside, energy-adjustable lumbar beef up is unavailable, and the not obligatory manually adjustable driver-facet lumbar toughen operates by the use of a labor-intensive knob.

in the audio department, the 6's usual stereo is just enough, and while the optional Bose gadget sounds markedly better, it lacks the clarity and wealthy bass response of the best stereos on this category. there may be better information on the cargo-carrying entrance, the place the sixteen.6-cubic-foot trunk units a new same old for domestic sedans. furthermore, it can be more desirable with the aid of upscale strut helps that do not impinge on the cargo area, and the 60/40-cut up-folding rear seats add to the 6's impressive hauling capabilities.
mazda 6 extended warranty
A awesome quantity of highway noise filters into the 6's cabin at velocity. Pavement imperfections barely ruffle the 6's composure, although, even when it is equipped with the non-compulsory 18-inch wheels. the bottom 2.5-liter engine produces wheezy noises and tepid acceleration, though the slick-shifting six-speed handbook shifter livens things up a little. The 5-pace automated is much less engaging but offers remarkably refined shifts. the large 3.7-liter V6 feels and sounds muscular, but it's a clean operator, even at greater engine speeds. unluckily, the six-pace computerized is not tuned for enthusiastic using -- downshifts are delayed, even in guide mode. handling is spectacular for a big household sedan, however the 6 would not really feel as tossable in corners as the Altima, and its guidance is lighter and looser than the nimble Nissan's. there may be most likely sufficient zoom on this chassis to placate folks that like to pressure, whereas the average client will relish the 6's reasonably compliant journey.
Categories: DBA Blogs

2016 Mazda6 Interior Review

EBIZ SIG BLOG - Wed, 2014-10-01 01:15
If there's an ethical to the absolutely redesigned 2016 Mazda6 Interior Review  story, it's that there may be extra to lifestyles than "zoom-zoom." The previous-generation Mazda 6 had a whole lot of it, yet Mazda had a satan of a time getting the shopping for public to notice. which is as a result of American drivers usually do not care a lot about how their domestic sedans behave on winding united states of america roads. What they want is space, security, reliability, energy and magnificence -- and while the outdated 6 looked nice sufficient, its tight dimensions and lackluster acceleration averted it from succeeding in an increasingly more competitive marketplace.

the new 6 demonstrates that Mazda wasn't going to make the identical mistake twice. want room to chill out? It bargains one of the vital accommodating cabins of any midsize sedan, with Texas-sized front seats and a backseat match for 6-footers. acquired baggage, or in all probability 4 units of golf golf equipment? The midsize Mazda now options an impressively massive 16.6 cubic toes of trunk space. need energy? Mazda's received you covered with the biggest and strongest V6 on this worth bracket, though its gasoline financial system is disappointing. need to make a way commentary? then you definately shouldn't be shopping for a family sedan within the first position. but as such cars go, we think the brand new 6 manages to be tautly horny, in particular from the front, despite its additional 6.1 inches of length and 2.three inches of width. in contrast to the previous model, the 2016 Mazda6 Interior Review  used to be engineered namely for the North American market -- and it shows.

It additionally method introduced weight, as the enlarged 6 is roughly a hundred and fifty pounds heavier than its predecessor. yet you can nonetheless discover the sporty reflexes that consumers have come to expect from this efficiency-oriented brand. physique roll is minimal through domestic-sedan requirements, and the steerage is light however responsive. The 6 by no means allows you to omit its really extensive dimension, but its smartly-sorted chassis and light-on-its-ft character at pace places it 2nd most effective to the Nissan Altima within the fun-to-force category.

Wait a minute, you might be announcing -- how might the "zoom-zoom" household sedan fail to be the sportiest automobile in its class? Three causes: The Altima's significantly lighter, its physique motions are higher managed and its steering is tighter and more communicative. however so what? because the previous 6 validated (and the Toyota Camry continues to reveal), prime-notch riding dynamics don't a very best-promoting household sedan make. What the brand new 6 offers is the coveted combination of american-fashion measurement and energy, along with above-average handling for individuals who care about that kind of thing. authentic fans won't in finding the 6 to their liking -- however hiya, that is what the Mazdaspeed three is for.

in short, the 2009 Mazda 6 is at or close to the top of its class in most respects. As universal, although, we suggest check-riding as many rival models as conceivable earlier than making your resolution, including the Chevrolet Malibu, Honda Accord, Hyundai Sonata, Nissan Altima, Subaru Legacy and Toyota Camry. each has its own strengths and weaknesses, but few can suit the 6's all-round competence and attraction.
battery for mazda 6 key fob
The 2009 Mazda 6 is a entrance-wheel-pressure midsize sedan. There are seven trim ranges: i SV, i activity, i journeying, i Grand visiting, s recreation, s journeying and s Grand visiting. fashions with the i prefix include the 4-cylinder engine, whereas fashions with the s prefix come with the V6.

the worth leader i SV comes usual with sixteen-inch metal wheels, a manually top-adjustable driver seat, full power accessories, a six-speaker CD stereo machine with guidance-wheel-installed audio controls, air-conditioning and a tilt/telescoping steerage column. The i recreation adds cruise keep an eye on, an auxiliary enter jack and keyless entry. The i traveling edition steps up the function content material with 17-inch alloy wheels, foglights, a commute pc, a power driver seat, keyless ignition/entry, electroluminescent gauges, black patterned accent pieces and a leather-based-wrapped steerage wheel and shift knob. The i Grand travelling model provides xenon headlights, heated leather seats with a reminiscence perform for the driving force seat, Bluetooth connectivity, twin-zone automatic climate regulate, auto-dimming mirrors and an auditory blind-spot monitoring device.

The s fashions feature the corresponding i models' usual gear together with just a few enhancements -- the s sport comes with 17-inch alloy wheels and dual exhaust retailers, and the s traveling and s Grand travelling add 18-inch alloy wheels.

A comfort package for visiting models tacks on most of the Grand visiting's standard luxuries, while the Moonroof and Bose bundle adds a sunroof and an upgraded audio system to journeying and Grand journeying fashions. A navigation system is to be had most effective on the Grand journeying. other choices include faraway start, an in-sprint six-CD changer and satellite tv for pc radio.
mazda 6 check engine light
The front-wheel-pressure 2009 Mazda 6 is powered through either a 2.5-liter 4-cylinder engine or a three.7-liter V6. The 4 generates 170 horsepower and 167 pound-feet of torque, while the V6 pumps out 272 hp and 269 lb-ft. A six-velocity manual transmission is standard on 4-cylinder fashions, with a five-velocity automated non-compulsory on all however the i SV. A six-velocity computerized is necessary on V6-powered models.

gasoline-economy estimates stand at 20 mpg metropolis/29 freeway and 23 mixed for 4-cylinder fashions with the manual transmission, while the five-speed auto improves the 4's numbers to 21 mpg metropolis/30 freeway and 24 blended. These are classification-competitive numbers. however, if you go for the V6, estimates drop to 17 mpg city/25 freeway and 20 mixed, which is ready as bad because it gets on this phase.
common problems with mazda 6
Antilock disc brakes, balance control, front-seat facet airbags and entire-length facet curtain airbags are all same old on the aftermarket mazda 6 parts.
difference between mazda 3 and mazda 6
The mazda 6 bluetooth issues control structure is in most cases intuitive, with all major knobs and buttons naturally labeled and simply manipulated. it's sexy, too, with crimson backlighting for the gauges and a swish middle stack sweeping ahead towards the windshield, despite the fact that the atypical black-and-silver patterned plastic trim in journeying models and above is not going to strike everyone's fancy. materials high quality is hit-or-pass over, as the wealthy-feeling soft-contact subject material on the passenger side of the dashboard contrasts with low-cost arduous stuff on the driving force aspect. The emergency brake additionally feels a bit chintzy for this value point. The generously proportioned seats are somewhat at ease, then again, with abundant leg- and headroom all around. On the downside, energy-adjustable lumbar beef up is unavailable, and the not obligatory manually adjustable driver-facet lumbar toughen operates by the use of a labor-intensive knob.

in the audio department, the 6's usual stereo is just enough, and while the optional Bose gadget sounds markedly better, it lacks the clarity and wealthy bass response of the best stereos on this category. there may be better information on the cargo-carrying entrance, the place the sixteen.6-cubic-foot trunk units a new same old for domestic sedans. furthermore, it can be more desirable with the aid of upscale strut helps that do not impinge on the cargo area, and the 60/40-cut up-folding rear seats add to the 6's impressive hauling capabilities.
mazda 6 extended warranty
A awesome quantity of highway noise filters into the 6's cabin at velocity. Pavement imperfections barely ruffle the 6's composure, although, even when it is equipped with the non-compulsory 18-inch wheels. the bottom 2.5-liter engine produces wheezy noises and tepid acceleration, though the slick-shifting six-speed handbook shifter livens things up a little. The 5-pace automated is much less engaging but offers remarkably refined shifts. the large 3.7-liter V6 feels and sounds muscular, but it's a clean operator, even at greater engine speeds. unluckily, the six-pace computerized is not tuned for enthusiastic using -- downshifts are delayed, even in guide mode. handling is spectacular for a big household sedan, however the 6 would not really feel as tossable in corners as the Altima, and its guidance is lighter and looser than the nimble Nissan's. there may be most likely sufficient zoom on this chassis to placate folks that like to pressure, whereas the average client will relish the 6's reasonably compliant journey.
Categories: APPS Blogs

Oracle Technology Network Tuesday in Review / Wednesday Preview - Oracle OpenWorld and JavaOne

OTN TechBlog - Wed, 2014-10-01 00:47


Another Day of Oracle OpenWorld and JavaOne comes to a close.  The OTN Wearable Meetup was great thanks to the Oracle Usable Apps team and the folks who came and showed us their wearable tech. 

Special Activity in the OTN lounge, Moscone South Upper Lobby for Wednesday October 1st -

Oracle Spatial and Graph users Meetup – 4 to 5pm
Meet the product managers, developers, and other users of Oracle's Spatial, Graph, and Multimedia Database technologies in these informal meetups. Share your questions, experiences, and ideas. Experts will listen to your product feedback and answer questions about
•    Spatial and MapViewer features for location-enabled business apps and GIS systems. Hosted by the IOUG Oracle Spatial Special Interest Group
•    RDF Graph for social network, semantic, and linked data applications
•    Multimedia for image archives, medical image applications, and other media-related applications

Out of the OTN Lounge -

Annual Blogger Meetup - 5:30pm to 7pm - Jillian @ Metreon

Oracle OpenWorld 2014 – Datatype context…?!

Marco Gralike - Tue, 2014-09-30 20:26
The native JSON database functionality presentations are done. If you want to experience first hand…

OOW14 Day 2 - Delphix #cloneattack

Yann Neuhaus - Tue, 2014-09-30 19:14

Do you know Delphix? The first time I heard of it was from Jonathan Lewis. And from Kyle Hailey of course. So it's not only about agile and virtualization. It's a real DBA stuff. So as I did yesterday with Dbvisit #repattack let's install the demo.

Here is the setup:

  • one source virtual machine with an XE database
  • one target virtual machine with XE installed but no database
  • one virtual machine with Delphix
And what can we do with that? We can clone the databases instantaneously. It's:
  • a virtual appliance managing storage snapshots for instant cloning
  • this is exposed through direct NFS to be used by the database
  • totally automated database maintenance (creating, restore, changing name, etc) through a nice GUI
So what's the point? You want to clone an environment instantaneously. Chose the point in time you want and it's done. You can clone 50 databases for your 50 developers. You can rewind your test database to run unit testing in an continuous integration development environment. You can do all that stuff that requires so many IT procedures just with a few clicks on the Delphix GUI.   Just an example, here is my source database and the way I choose the point in time I want to clone:   CaptureDelphix01.PNG   It's running: CaptureDelphix02.PNG   The #cloneattack is a good way to test things and discuss with others...  

I have now @delphix on my laptop installed with @kylehhailey at #oow14. Cont. tomorrow at OTW http://t.co/QJLVhp93jg pic.twitter.com/QgoAgJPXyo

— Franck Pachot (@FranckPachot) September 30, 2014

@kylehhailey #cloneattack: finished it today now playing with clones while listening to @TanelPoder pic.twitter.com/wH3kQKBp8U

— Franck Pachot (@FranckPachot) September 30, 2014

That's some powerful multitasking - awesome @FranckPachot @TanelPoder

— Kyle Hailey (@kylehhailey) September 30, 2014