Version imprimable
Bonjour,
Depuis une semaine, j'ai un export de base de données qui est assez long.
Avant il mettait une 10 de minutes maintenant il met 3 heures. Rien n'a changé dans le script.
Il est très long sur des tables qui font 0 lignes et 0 Ko.
Pour info le dump tourne autour de 2 Go.
Avez vous une idée ?
merci.
AprentiOracle
Les waits de expdp :
Pièce jointe 178145
Si vous êtes en 12.1.0.1, vous pourriez être concerné par le cas suivant :
"Bug 18469379 - Data pump export estimate phase takes a long time to determine if table is empty (Fixed in 12.1.0.2)"
Et donc il faudrait passer en 12.1.0.2.
Effectivement je suis en 12.1.0.1.Citation:
Envoyé par Pomalaix
Est ce que ce patch, va "toucher" quelques choses sur la base proprement dite ou elle va "juste" ajouter des choses sur le moteur oracle ?
merci pour votre retour Pomalaix.
Oui, il y a des mises à jour en base, mais qui ne sont pas censées toucher vos données.Citation:
Envoyé par ApprentiOracle
Néanmoins, il faut comme toujours tester l'opération sur une machine de validation, effectuer une sauvegarde de la base avant les mises à niveau, etc.
OK. Merci.
Mais je croyais à la lecture du readme du patch que juste le moteur oracle était modifié car jamais il est indiqué de renseigné un ORACLE_SID.
Citation:
Oracle Database 12c Release 12.1.0.1.0
ORACLE DATABASE Patch for Bug# 18469379 for Generic Platforms
This patch is non-RAC Rolling Installable.
This patch is Data Guard Standby-First Installable - Please read My Oracle Support Note 1265700.1 https://support.us.oracle.com/oip/fa...x?id=1265700.1
Oracle Patch Assurance - Data Guard Standby-First Patch Apply for details on how to remove risk and reduce downtime when applying this patch.
Released: Fri May 9 12:14:47 2014
This document describes how you can install the ORACLE DATABASE interim patch for bug# 18469379 on your Oracle Database 12c Release 12.1.0.1.0
(I) Prerequisites
--------------------
Before you install or deinstall the patch, ensure that you meet the following requirements:
Note: In case of an Oracle RAC environment, meet these prerequisites on each of the nodes.
1. Ensure that the Oracle home on which you are installing the patch or from which you are rolling back the patch is Oracle Database 12c Release 12.1.0.1.0.
2. Oracle recommends that you use the latest version available for 12c Release 12.1.0.1.0. If you do not have OPatch 12c Release 12.1.0.1.0 or the latest version available for 12c Release 12.1.0.1.0,then download it from patch# 6880880 for 12.1.0.1.0 release.
For information about OPatch documentation, including any known issues, see My Oracle Support Document 293369.1 OPatch documentation list:
https://support.oracle.com/CSP/main/...OT&id=224346.1
3. Ensure that you set (as the home user) the ORACLE_HOME environment variable to the Oracle home.
4. Ensure that the $PATH definition has the following executables: make, ar, ld and nm. The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin.
5. Ensure that you verify the Oracle Inventory because OPatch accesses it to install the patches. To verify the inventory, run the following command.
$ opatch lsinventory
Note:
- If this command succeeds, it will list the Top-Level Oracle Products and one-off patches if any that are installed in the Oralce Home.
- Save the output so you have the status prior to the patch apply.
- If the command displays some errors, then contact Oracle Support and resolve the issue first before proceeding further.
6. (Only for Installation) Maintain a location for storing the contents of the patch ZIP file. In the rest of the document, this location (absolute path) is referred to as <PATCH_TOP_DIR>. Extract the contents of the patch ZIP file to the location (PATCH_TOP_DIR) you have created above. To do so, run the following command:
$ unzip -d <PATCH_TOP_DIR> p18469379_121010_Generic.zip
7. (Only for Installation) Determine whether any currently installed interim patches conflict with this patch 18469379 as shown below:
$ cd <PATCH_TOP_DIR>/18469379
$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./
The report will indicate the patches that conflict with this patch and the patches for which the current 18469379 is a superset.
Note:
When OPatch starts, it validates the patch and ensures that there are no conflicts with the software already installed in the ORACLE_HOME. OPatch categorizes conflicts into the following types:
- Conflicts with a patch already applied to the ORACLE_HOME that is a subset of the patch you are trying to apply - In this case, continue with the patch installation because the new patch contains all the fixes from the existing patch in the ORACLE_HOME. The subset patch will automatically be rolled back prior to the installation of the new patch.
- Conflicts with a patch already applied to the ORACLE_HOME - In this case, stop the patch installation and contact Oracle Support Services.
(II) Installation
-----------------
To install the patch, follow these steps:
1. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
$ cd <PATCH_TOP_DIR>/18469379
$ opatch apply
2. Verify whether the patch has been successfully installed by running the following command:
$ opatch lsinventory
(III) Postinstallation
---------------------
Note: In case of an Oracle RAC environment, perform these steps on each of the nodes.
1. Navigate to the <ORACLE_HOME>/OPatch directory:
$ cd <ORACLE_HOME>/OPatch
2. Install the SQL portion of the patch by running the following command:
$ datapatch
(IV) Deinstallation
----------------------
Ensure to follow the Prerequsites (Section I). To deinstall the patch, follow these steps:
1. Deinstall the patch by running the following command:
$ opatch rollback -id 18469379
2. Ensure that you verify the Oracle Inventory and compare the output with the one run before the patch installation and re-apply any patches that were rolled back as part of this patch apply. To verify the inventory, run the following command:
$ opatch lsinventory
(V) Postdeinstallation
-----------------------
(VI) Bugs Fixed by This Patch
---------------------------------
The following are the bugs fixed by this patch:
18469379: DATA PUMP EXPORT ESTIMATE PHASE TAKES A LONG TIME TO DETERMINE IF TABLE IS EMPTY
--------------------------------------------------------------------------
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
--------------------------------------------------------------------------
C'est juste qu'on ne parlait pas de la même chose !Citation:
Envoyé par ApprentiOracle
Vous, vous parlez de l'application d'un patch individuel, et moi je parlais de la procédure de passage en 12.1.0.2.
Bien entendu, s'il y a un correctif ciblé, c'est lui qu'il faut prendre.
Ok merci, je comprends mieux !
Donc uniquement le moteur devrait etre touché en installant le petit patch ?
Savez vous ce que fait le datapatch ? Ecrit il des données ou fait il des modifications directement en base ? Parce qu'il y a noté "Install the SQL portion of the patch by running the following command:"
merci.
Citation:
(III) Postinstallation
---------------------
Note: In case of an Oracle RAC environment, perform these steps on each of the nodes.
1. Navigate to the <ORACLE_HOME>/OPatch directory:
$ cd <ORACLE_HOME>/OPatch
2. Install the SQL portion of the patch by running the following command:
$ datapatch
Bonjour,
La 12.1.0.2 n'existe pas encore pour la Standard Edition. Aux dernières rumeurs (de gens fiables) on devrait l'avoir fin juin.Citation:
Envoyé par Pomalaix
Cordialement,
Franck.
