Feed aggregator

12c DataGuard Validate and More

Michael Dinh - Fri, 2017-06-16 18:11
12c Dataguard Switchover Best Practices using DGMGRL(Dataguard Broker Command Prompt) (Doc ID 1582837.1)	

db_unique_name=hawka (primary)
db_unique_name=hawkb (standby)

Configuration - hawkdg
  Protection Mode: MaxPerformance
    hawka - Primary database
      hawkb - Physical standby database 

Validate DataGuard Configurations.

Monitorable (Read-Only) Properties

show configuration verbose

show database verbose hawka
show database verbose hawkb

validate database verbose hawka
validate database verbose hawkb

There is no need to use on database if the instance names are unique across primary and standby environments.

You might ask, why are instance name not the  same on primary and standby?

I don’t know.

show instance verbose hawka1 on database hawka
show instance verbose hawka2 on database hawka

show instance verbose hawkb1 on database hawkb
show instance verbose hawkb2 on database hawkb

The InconsistentProperties monitorable property returns a table that shows all properties whose values contained in the broker configuration file are inconsistent with the values in the corresponding server parameter file or the runtime values.

show database hawka InconsistentProperties
show database hawkb InconsistentProperties

The InconsistentLogXptProps monitorable property returns a table that shows all properties related to redo transport services whose values are inconsistent between the broker configuration file and the runtime value.

show database hawka InconsistentLogXptProps
show database hawkb InconsistentLogXptProps

The LogXptStatus monitorable property returns a table that contains the error status of redo transport services for each of the enabled configuration members. This property pertains to the primary database, a physical standby database that ships redo data, or a far sync instance.

show database hawka LogXptStatus

The SendQEntries monitorable property returns a table that shows all log files on the primary database that were not successfully archived to one or more standby databases. This property pertains to the primary database

show database hawka SendQEntries

The RecvQEntries monitorable property returns a table indicating all log files that were received by the standby database but have not yet been applied. If no rows are returned, it implies all log files received have been applied. This property pertains to a standby database.

show database hawkb RecvQEntries

The TopWaitEvents monitorable property specifies the 5 events with the longest waiting time in the specified instance.

show instance hawkb1 TopWaitEvents

How to edit database properties for all instances.

edit instance * on database hawka set property logarchivetrace=0;

Lastly, all commands and be run from shell script with example below.

echo "***** Checking Data Guard Broker Configuration ...."
dgmgrl -echo << END
connect /
show configuration verbose
show configuration TraceLevel
show database hawklas
show database hawksan
show instance hawklas DGConnectIdentifier
show instance hawksan DGConnectIdentifier
show instance hawklas StaticConnectIdentifier
show instance hawksan StaticConnectIdentifier
show instance hawklas InconsistentProperties
show instance hawksan InconsistentProperties
show instance hawklas LogArchiveMaxProcesses
show instance hawksan LogArchiveMaxProcesses
show instance hawklas DelayMins
show instance hawksan DelayMins
show instance hawklas LogArchiveTrace
show instance hawksan LogArchiveTrace
show instance hawklas statusreport
show instance hawksan statusreport

Range Partitioning Query

Tom Kyte - Fri, 2017-06-16 14:06
Hi Connor, After following Partitioning videos from KISS series started practicing on my own and have a query: In a Range partition, I want to create the partioining based on Country column and all values that belong to AU should go to AU_01 P...
Categories: DBA Blogs

Question on collection using outside of package

Tom Kyte - Fri, 2017-06-16 14:06
Hi , I have this requirement wherein I need to collect data in a collection in a PL/SQL package and use that collection in SQL * Plus in a query as shown in the below script.I was able to do by using cast(multiset). However I do not want to use th...
Categories: DBA Blogs

Unable to understand the Explain plan for a query

Tom Kyte - Fri, 2017-06-16 14:06
<code>Hi Tom, I recently started going into the performance tuning stuff, and that's when i got stuck at one of the explain plan. Below is the Explain plan: --------------------------------------------------------------------------------------...
Categories: DBA Blogs

Is NONLOGGING LOAD followed by INSERT into (logged) table recoverable ?

Tom Kyte - Fri, 2017-06-16 14:06
Having spent a while searching the AskTom archives, I cannot find an answer to this. In order for the following data-pipeline to be recoverable ( from a site-failure ) : do ALL operations have to be LOGGING or can we assume that only the final mov...
Categories: DBA Blogs

connection string needed in .net using Oracle wallet

Tom Kyte - Fri, 2017-06-16 14:06
What kind of connection string is needed in .net when using an Oracle Wallet? I have a unix server set up with an Oracle wallet that has the username/password of the user that will be connecting in the .net application. I modified the server sqln...
Categories: DBA Blogs

question about dataguard sync .

Tom Kyte - Fri, 2017-06-16 14:06
Hello? I have a question about sync attribute of ADG on Oracle doc says that transaction can commit only if primary db receive the ack from all destinations which set for sync. But our application wants commit as soon as posible when pr...
Categories: DBA Blogs

Log Buffer #514: A Carnival of the Vanities for DBAs

Pythian Group - Fri, 2017-06-16 13:19

This Log Buffer Edition encompasses few of the nifty blog posts from Oracle, SQL Server and MySQL.


Introduction to Oracle Big Data Cloud Service

Interpreting wpad.dat using jrunscript from JDK 8 to work out the right proxy.

Nice Trick to Get ADF LOV Description Text

Presentation: Dynamic Actions, Javascript, & CSS for APEX Beginners

E4 Session Developing Agnostic Data Services

SQL Server:

Setting up R in SQL 2016 – Avoiding Pitfalls

Setting Variables in Calling T-SQL Code While Using sp_executesql

To Fly, To Serve, To Fry Your Servers

Working with Windows Containers and Docker: Into your Stride

What is normal? Finding outliers with R

Two Approaches to Addressing Circular References in SSDT


Howto make MySQL point-in-time recovery faster ?

Three Methods of Installing Percona Monitoring and Management

Watch the tutorial: backup best practices for MySQL, MariaDB and Galera Cluster

MySQL 8.0: Kana-sensitive collation for Japanese

MySQL Document Store: Getting Started

Categories: DBA Blogs

Importance of BI tools for Pharmaceutical Industry

Nilesh Jethwa - Fri, 2017-06-16 12:40

The pharmaceutical industry has been focusing much of its energy on producing the next chartbusting drugs.

However, the industry is also facing challenges in terms of the changing regulations, increasing number of declines on drug approvals and the continuing need to develop high value biologics. Refocusing efforts is imperative.

There are existing processes, systems and practices that need to be immediately addressed. Key performance indicators (KPI) using BI tools help corporations identify areas that need continuous development and highlight successes already achieved. This helps pharmaceutical companies grasp their management operations better.

What is KPI?

Simply put, KPI is a measurement of something that is vital in a business’s operations. In the pharmaceutical industry, measurements on drug cost overall trend for a certain drug are examples of KPIs.

What KPIs to Include

Before using dashboard software to view KPIs, it is important that useful KPIs be identified first. Some KPIs are not useful to a certain organization, depending on the operations and the needs of that organization. It is therefore important to have long discussions first before operating a KPI dashboard. Discussions should tackle on:

  • Assessing the organization’s strategies.
  • Determining the business drives that have an impact on the execution of strategies.
  • Identification of long-term and short-term goals.

Determining useful KPIs is one the most important tasks of managers. KPIs based on the organization’s objectives are essential components of an effective and helpful dashboard. What you will see on the dashboard will largely depend on how you specify your KPIs.

Read more at http://www.infocaptor.com/dashboard/dashboard-bi-tools-for-pharmaceutical-industry

Generally available Kudu

DBMS2 - Fri, 2017-06-16 10:52

I talked with Cloudera about Kudu in early May. Besides giving me a lot of information about Kudu, Cloudera also helped confirm some trends I’m seeing elsewhere, including:

  • Security is an ever bigger deal.
  • There’s a lot of interest in data warehouses (perhaps really data marts) that are updated in human real-time.
    • Prospects for that respond well to the actual term “data warehouse”, at least when preceded by some modifier to suggest that it’s modern/low-latency/non-batch or whatever.
    • Flash is often — but not yet always — preferred over disk for that kind of use.
    • Sometimes these data stores are greenfield. When they’re migrations, they come more commonly from analytic RDBMS or data warehouse appliance (the most commonly mentioned ones are Teradata, Netezza and Vertica, but that’s perhaps just due to those product lines’ market share), rather than from general purpose DBMS such as Oracle or SQL Server.
  • Intel is making it ever easier to vectorize CPU operations, and analytic data managers are increasingly taking advantage of this possibility.

Now let’s talk about Kudu itself. As I discussed at length in September 2015, Kudu is:

  • A data storage system introduced by Cloudera (and subsequently open-sourced).
  • Columnar.
  • Updatable in human real-time.
  • Meant to serve as the data storage tier for Impala and Spark.

Kudu’s adoption and roll-out story starts:

  • Kudu went to general availability on January 31. I gather this spawned an uptick in trial activity.
  • A subsequent release with some basic security features spawned another uptick.
  • I don’t think Cloudera will mind my saying that there are many hundreds of active Kudu clusters.
  • But Cloudera believes that, this soon after GA, very few Kudu users are in actual production.

Early Kudu interest is focused on 2-3 kinds of use case. The biggest is the kind of “data warehousing” highlighted above. Cloudera characterizes the others by the kinds of data stored, specifically the overlapping categories of time series — including financial trading — and machine-generated data. A lot of early Kudu use is with Spark, even ahead of (or in conjunction with) Impala. A small amount has no relational front-end at all.

Other notes on Kudu include:

  • Solid-state storage is recommended, with a few terabytes per node.
  • You can also use spinning disk. If you do, your write-ahead logs can still go to flash.
  • Cloudera said Kudu compression ratios can be as low as 2-5X, or as high as 10-20X. With that broad a range, I didn’t drill down into specifics of what they meant.
  • There seem to be a number of Kudu clusters with 50+ nodes each. By way of contrast, a “typical” Cloudera customer has 100s of nodes overall.
  • As you might imagine from their newness, Kudu security features — Kerberos-based — are at the database level rather than anything more granular.

And finally, the Cloudera folks woke me up to some issues around streaming data ingest. If you stream data in, there will be retries resulting in duplicate delivery. So your system needs to deal with those one way or another. Kudu’s way is:

  • Primary keys will be unique. (Note: This is not obvious in a system that isn’t an entire RDBMS in itself.)
  • You can configure the uniqueness to be guaranteed either through an upsert mechanism or just by simply rejecting duplicates.
  • Alternatively, you can write code to handle duplication errors, e.g. via Spark.
Categories: Other

DBSAT un outil pour la sécurité de vos bases de données Oracle

Yann Neuhaus - Fri, 2017-06-16 10:22
Qu’est-ce que DBSAT ?

C’est un outil gratuit d’Oracle que vous pouvez télécharger sur My Oracle Support avec comme référence : Doc Id 2138254.1.
Il a pour but d’évaluer la sécurité de vos bases de données Oracle en analysant la configuration et les stratégies de sécurité mise en place afin de découvrir les risques liés à la sécurité.

Comment cela fonctionne t-il ?

Dans un premier temps il sera nécessaire de collecter les informations de votre database et dans un second temps de générer un rapport.
L’outil met à notre disposition 3 types de rapport.

  • Rapport Texte
  • Rapport Tableau
  • Rapport HTML

En quelques mots :

  • Implémentation et utilisation facile et rapide
  • Rapports détaillés
  • Détecte de véritable problème de sécurité
  • Pas de coûts supplémentaires si vous avez avez un contrat de support Oracle
  • Les résultats sont mis en évidence par différentes couleurs (Bleu, Vert, Jaune, Rouge)
Les différentes étapes nécessaires à la mise en œuvre
  • Installation de l’outil (DBSAT)
  • Collection des informations (DBSAT Collector)
  • Rapport sur l’état des risques (DBSAT Reports)
Installation de l’outil

Cet outil est développé en Python est requiert la version 2.6 ou supérieure (voir la version : python -V).

Le répertoire d’installation peut être ou vous le souhaitez car l’installation n’est qu’une décompression d’un fichier zippé, mais nous vous conseillons de le décompresser dans le répertoire de l’utilisateur  Oracle (/Home/Oracle/DBSAT).

DBSAT Collector doit être exécuté en tant qu’utilisateur OS avec des autorisations de lecture sur les fichiers et les répertoires sous ORACLE_HOME afin de collecter et traiter les données.

Si vous utilisez un environnement Vault il sera nécessaire d’utiliser un utilisateur non-SYS avec le role DV_SECANALYST.


    • Role DV_SECANALYST (if Database Vault is enabled)
    • Role AUDIT_VIEWER (12c only)
    • Role CAPTURE_ADMIN (12c only)
    • SELECT on SYS.DBA_USERS_WITH_DEFPWD (11g and 12c)
    • SELECT on AUDSYS.AUD$UNIFIED (12c only)

Vous trouverez plus d’information dans la documentation à l’adresse suivante :

Collection des informations

La collection des informations est obligatoire. Celle-ci sera nécessaire pour la génération des rapports (Texte, HTML ou Tableau).
Très simple à utiliser et sécurisé : dbsat collect /file_name
Capture d’écran 2017-06-09 à 17.00.00

Rapport sur l’état des risques

Le rapport peut être généré de différentes manière en excluant plusieurs sections avec l’option -x.
dbsat report [-a] [-n] [-x section] pathname

Options :
Capture d’écran 2017-06-12 à 17.52.53

Les différentes sections utilisables

USER     : Compte utilisateur
PRIV      : Privileges et Roles
AUTH     : Contrôles authorisations
CRYPT    : Encryption des données
ACCESS  : Contrôle d’accès
AUDIT    : Audit
CONF      : Configuration Base de données
NET         : Configuration réseaux
OS            : Système d’exploitation

Capture d’écran 2017-06-09 à 17.31.14
Une fois décompressé, nous avons nos 3 types de fichier, texte, tableau et html.

Capture d’écran 2017-06-09 à 17.35.39

 Consultation du rapport

Aperçu du rapport.
Si vous utilisez des PDB, il sera nécessaire de collecter les informations auprès de chaque PDB individuellement.

Capture d’écran 2017-06-12 à 17.11.04

Capture d’écran 2017-06-12 à 17.14.03Les différents status du rapport

Vous pouvez utiliser ces status comme un fil rouge pour la mise en œuvre de recommandation. Ceci peut être utilisé pour prioriser et  planifier les modifications en fonction du niveau de risque. Un risque grave pourrait nécessiter des mesures correctives immédiates, alors que d’autres risques pourraient être résolus pendant un temps d’arrêt planifié ou associés à d’autres activités de maintenance.

Passe             : Aucune erreur trouvée
Évaluation   : Nécessite une analyse manuelle
Risque           : Bas
Risque           : Medium significatif
Risque           : Haut


Testez-le sans modération, il vous permettra d’avoir une vue globale sur la mise en place de la sécurité de vos bases de données. Une fois les problèmes identifiés il ne vous restera plus qu’à les corriger.


Cet article DBSAT un outil pour la sécurité de vos bases de données Oracle est apparu en premier sur Blog dbi services.

Video: Chatbot Challenges - A Human Conversation

OTN TechBlog - Fri, 2017-06-16 10:07

Chatbots won't make you rich, according to Frank Nimphius, Senior Principal Product Manager in the Oracle Mobile Platform Group. That takes a good business model. "But once you have a good business model, a chatbot can really help you to reach out to an audience that otherwise might not be interested in doing business with you," Frank says. Like millenials.

But as Frank explains, developing chatbots is not without its challenges. One such challenge is identifying design patterns that work with chatbots, just as there are design patterns for web applications and mobile applications. 

Another challenge Frank identifies is getting all of the artificial intelligence and machine learning that is required to understand natural language to work in the context of the application you're building. Will you have to get several technologies and put them together? Will you have to learn a lot of APIs?

Frank explores those issues and more in this interview recorded at the Oracle Code event in Toronto on April 18, 2017. Watch!

Additional Resources


OUD – How to create an OUD Start/Stop/Status script on Oracle Linux 6

Yann Neuhaus - Fri, 2017-06-16 08:39

One of the questions that pops up immediately, after you have installed your OUD successfully is how to integrate it into the automatic startup routines of the OS.

My example here show how to do it on Oracle Linux 6. On Oracle Linux 7 it looks a little different. Fortunately, Oracle delivers a script called “create-rc-script”, which can be found in your asinst home directory. It lets you specify the user name under which the OUD will run, the JAVA home and few more stuff. The whole documentation can be found under the following link.


Running “–help” gives you all the options.

$ cat /etc/oracle-release
Oracle Linux Server release 6.9

$ ./create-rc-script -V
Oracle Unified Directory
Build 20170206221556Z

$ ./create-rc-script --help
Create an RC script that may be used to start, stop, and restart the Directory
Server on UNIX-based systems

Usage:  create-rc-script  {options}
        where {options} include:

-f, --outputFile {path}
    The path to the output file to create
-u, --userName {userName}
    The name of the user account under which the server should run
-j, --javaHome {path}
    The path to the Java installation that should be used to run the server
-J, --javaArgs {args}
    A set of arguments that should be passed to the JVM when running the server

General Options

-V, --version
    Display Directory Server version information
-?, -H, --help
    Display this usage information

Take care that you start the “create-rc-script” script from your asinst_1 home, and not from the Oracle_OUD1 home. The reason for that, is that the “create-rc-script” sets the working directory to your current directory. “WORKING_DIR=`pwd`”, and if not started from the correct directory, you might end up with a not working start/stop script.

So .. to do it correctly, switch to your OUD asinst home first and run it from there. I am using here only a few options. The JAVA home, the user name under which the OUD will run and the output file.

$ cd /u01/app/oracle/product/middleware/asinst_1/OUD/bin

$ pwd

$ ./create-rc-script --userName oracle --javaHome /u01/app/oracle/product/middleware/jdk --outputFile /home/oracle/bin/oud

The output generated by the script will be the start/stop script.

$ pwd

$ ls -l
total 4
-rwxr-xr-x. 1 oracle oinstall 862 Jun 16 13:35 oud

$ cat oud
# Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
# chkconfig: 345 90 30
# description: Oracle Unified Directory startup script

# Set the path to the Oracle Unified Directory instance to manage

# Specify the path to the Java installation to use

# Determine what action should be performed on the server
case "${1}" in
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/start-ds" --quiet
  exit ${?}
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/stop-ds" --quiet
  exit ${?}
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/stop-ds" --restart --quiet
  exit ${?}
  echo "Usage:  $0 { start | stop | restart }"
  exit 1

The generated start/stop script looks quite complete. The only thing missing is the “status” section which is quite useful from my point of view. To add the status section, we can use the “status” script, which is also part of the OUD installation.

$ ./status --help
This utility can be used to display basic server information

Usage:  status {options}
        where {options} include:

LDAP Connection Options

-D, --bindDN {bindDN}
    DN to use to bind to the server
    Default value: cn=Directory Manager
-j, --bindPasswordFile {bindPasswordFile}
    Bind password file
-o, --saslOption {name=value}
    SASL bind options
-X, --trustAll
    Trust all server SSL certificates
-P, --trustStorePath {trustStorePath}
    Certificate trust store path
-U, --trustStorePasswordFile {path}
    Certificate trust store PIN file
-K, --keyStorePath {keyStorePath}
    Certificate key store path
-u, --keyStorePasswordFile {keyStorePasswordFile}
    Certificate key store PIN file
-N, --certNickname {nickname}
    Nickname of certificate for SSL client authentication
--connectTimeout {timeout}
    Maximum length of time (in milliseconds) that can be taken to establish a
    connection.  Use '0' to specify no time out
    Default value: 30000

Utility Input/Output Options

-n, --no-prompt
    Use non-interactive mode.  If data in the command is missing, the user is
    not prompted and the tool will fail
-s, --script-friendly
    Use script-friendly mode
--propertiesFilePath {propertiesFilePath}
    Path to the file containing default property values used for command line
    No properties file will be used to get default command line argument values
-r, --refresh {period}
    When this argument is specified, the status command will display its
    contents periodically.  Used to specify the period (in seconds) between two
    displays of the status

General Options

-V, --version
    Display Directory Server version information
-?, -H, --help
    Display this usage information

Take care. Per default, the status utility is an interactive one, and it asks you for the user bind DN and the password. So, the interactive version of that script is not useful for our script.

$ ./status

>>>> Specify Oracle Unified Directory LDAP connection parameters

Administrator user bind DN [cn=Directory Manager]:

Password for user 'cn=Directory Manager':

          --- Server Status ---
Server Run Status:        Started
Open Connections:         6

          --- Server Details ---
Host Name:                dbidg01
Administrative Users:     cn=Directory Manager
Installation Path:        /u01/app/oracle/product/middleware/Oracle_OUD1
Instance Path:            /u01/app/oracle/product/middleware/asinst_1/OUD
Version:                  Oracle Unified Directory
Java Version:             1.7.0_141
Administration Connector: Port 4444 (LDAPS)

          --- Connection Handlers ---
Address:Port : Protocol               : State
--           : LDIF                   : Disabled
8899         : Replication (secure)   : Enabled  : SNMP                   : Disabled : LDAP (allows StartTLS) : Enabled : LDAPS                  : Enabled : JMX                    : Disabled

And we need to do some adjustments, like in the following example.

./status --trustAll --no-prompt --bindDN cn="Directory Manager" --bindPasswordFile /home/oracle/.oudpwd | head -24

OK. To complete the script, we can add the status section to the script.

$ cat oud

# Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
# chkconfig: 345 90 30
# description: Oracle Unified Directory startup script

# Set the path to the Oracle Unified Directory instance to manage

# Specify the path to the Java installation to use

# Determine what action should be performed on the server
case "${1}" in
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/start-ds" --quiet
  exit ${?}
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/stop-ds" --quiet
  exit ${?}
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/stop-ds" --restart --quiet
  exit ${?}
  /bin/su - oracle -- "${INSTALL_ROOT}/bin/status" --trustAll --no-prompt --bindDN cn="Directory Manager" --bindPasswordFile /home/oracle/.oudpwd | head -24
  exit ${?}
  echo "Usage:  $0 { start | stop | restart | status }"
  exit 1

Last but not least, we need to move it with the root user to the /etc/init.d directory and add it via chkconfig.

# mv /home/oracle/bin/oud /etc/init.d/
# chkconfig --add oud

# chkconfig --list | grep oud
oud             0:off   1:off   2:off   3:on    4:on    5:on    6:off

That’s all. The OUD part is done now. But what about the ODSM? We want the WebLogic domain to startup automatically as well. For doing so, we need another script.

$ cat /home/oracle/bin/weblogic

# chkconfig: 345 90 30
# description: WebLogic 10.3.6 startup script

# Specify the path to the Java installation to use
export JAVA_HOME


# Determine what action should be performed on the server
case "${1}" in
  /bin/su - oracle -c "nohup ${BASE_DOMAIN}/bin/startWebLogic.sh &"
  exit ${?}
  /bin/su - oracle -c "${BASE_DOMAIN}/bin/stopWebLogic.sh"
  exit ${?}
  /bin/su - oracle -c "${BASE_DOMAIN}/bin/stopWebLogic.sh"
  /bin/su - oracle -c "nohup ${BASE_DOMAIN}/bin/startWebLogic.sh &"
  exit ${?}
  echo "Usage:  $0 { start | stop | restart }"
  exit 1

Now it’s time to move the weblogic to the start routines as well.

# mv /home/oracle/bin/weblogic /etc/init.d/
# chkconfig --add weblogic
# chkconfig --list | grep weblogic
weblogic        0:off   1:off   2:off   3:on    4:on    5:on    6:off

After everything is setup, it is time to test it. ;-)

# chkconfig --list | egrep '(weblogic|oud)'
oud             0:off   1:off   2:off   3:on    4:on    5:on    6:off
weblogic        0:off   1:off   2:off   3:on    4:on    5:on    6:off

# init 6

Now just check if everything came up correctly.


The OUD comes with a script “create-rc-script” which is quite useful. However, in case you have the OSDM and you want the OUD status section as well, some adjustments have to be done.


Cet article OUD – How to create an OUD Start/Stop/Status script on Oracle Linux 6 est apparu en premier sur Blog dbi services.


LogicaCMG - Fri, 2017-06-16 03:39










Webcast: Testing Recommendations for Oracle E-Business Suite Applications

Steven Chan - Fri, 2017-06-16 02:00

Oracle University has a large collection of free recorded webcasts that EBS system administrators might find useful. Here's another webcast on testing EBS environments:

Prashanti Madiredd, Senior Director Quality Assurance shares best practices from the Oracle E-Business Suite Development team on the following topics: how the Oracle Development Quality Assurance team tests Oracle E-Business Suite, factors for customers to consider during functional testing, approaches for new feature and regression testing, reducing risk and production outages due to insufficient testing, capturing and presenting metrics to showcase the ROI of testing investment and leveraging automation for testing Oracle E-Business Suite application. This material was presented at Oracle OpenWorld 2014.

Related Articles


Categories: APPS Blogs

No data is logged in flashback_transaction_query view

Tom Kyte - Thu, 2017-06-15 19:46
Hi, I have been using flashback_transaction_query view since the previous version but in 12.1.0, I got the strange situation that is not explained with any reference. As far as I know, user has to enable supplemental logging to log some flashba...
Categories: DBA Blogs

login as sysdba remotely without any other prompts / or grant a user for example system shutdown and startup privilege

Tom Kyte - Thu, 2017-06-15 19:46
Hi , we are testing remote db setup and from application team we have to run scripts which were using sysdba earlier , but now we want to run those same scripts on a remote db from a application machine . So there are few places where we have to s...
Categories: DBA Blogs

Update statement with correlated subquery that intentionally passes multiple rows

Tom Kyte - Thu, 2017-06-15 19:46
I am trying to update one table using a subquery that totals several transactions from another table. I cannot figure how to link specific rows from my parent table to the rows in my subquery. I keep getting the ORA-01427: Subquery returns more than ...
Categories: DBA Blogs

HIUG Interact 2017

Jim Marion - Thu, 2017-06-15 16:11

Are you attending Interact 2017 this weekend? I will be leading a PeopleTools hands-on workshop on Sunday from 1:30 PM to 4:30 PM in Panzacola F-4. Because this is hands-on, please bring your laptop. All session activities will be completed over a remote desktop connection, so as long as you have a Remote Desktop Client and a full battery charge, you should be ready. In this session we will cover a variety of topics including classic global and component branding as well as fluid navigation and page development. I look forward to seeing you in Orlando!

OGh Tech Experience 2017 : Day 1 – Rumours of my demise

Tim Hall - Thu, 2017-06-15 12:39

For those that missed me, I did actually turn up to the event today. I arrived at about 11:00, got my badge, sat down in the speaker room for a bout 2 minutes, then left and came back to the hotel.

I was ill most of last week and I thought I was a lot better, but the flight yesterday and the heat since I’ve been here have really put me back. My sinuses feel like they are going to explode and I have zero energy.

I seem to be jinxed where the Netherlands are concerned. Last year I got ill between the AMIS and OGh events. This time it’s come slap bang on the OGh event.

Unless something changes drastically overnight, my plan for tomorrow is to arrive late, do my two presentations, then leave and get back to bed. I fly home the following morning.



OGh Tech Experience 2017 : Day 1 – Rumours of my demise was first posted on June 15, 2017 at 6:39 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.


Subscribe to Oracle FAQ aggregator