ORA-04080: trigger ‘PRICE_HISTORY_TRIGGERV1’ does not exist

It is actually a dumb one. I was disabling triggers in a schema and ran this SQL to generate the disable statements. (Example from here) HR@test> select 'alter trigger '||trigger_name|| ' disable;' from user_triggers where table_name='PRODUCT'; 'ALTERTRIGGER'||TRIGGER_NAME||'DISABLE;' -------------------------------------------------------------------------------- alter trigger PRICE_HISTORY_TRIGGERv1 disable; HR@test> alter trigger PRICE_HISTORY_TRIGGERv1 disable; alter trigger PRICE_HISTORY_TRIGGERv1 disable * ERROR at line 1: ORA-04080: trigger 'PRICE_HISTORY_TRIGGERV1' does not exist HR@test> WTF ? It is there but the disable didn’t work. I was in hurry, tried to connect through SQL developer and disable and it worked ! Double WTF ! Then i spotted the problem. Someone created it with one letter in the name in small. So to make it work, we need to use double quotes. ...

January 22, 2019 at 7:15 PM · 1 min · 143 words · Amardeep Sidhu

Error while running ggsci

This was another issue that I faced while trying to configure GoldenGate in HA mode. ggsci was working fine after normal installation but after configuring it in HA mode and trying to run ggsci, it resulted in this: [oragg@node2 product]$ ggsci Oracle GoldenGate Command Interpreter for Oracle Version 12.3.0.1.4 OGGCORE_12.3.0.1.0_PLATFORMS_180415.0359_FBO Linux, x64, 64bit (optimized), Oracle 12c on Apr 16 2018 00:53:30 Operating system character set identified as UTF-8. Copyright (C) 1995, 2018, Oracle and/or its affiliates. All rights reserved. 2019-01-08 16:28:37.913 CLSD: An error occurred while attempting to generate a full name. Logging may not be active for this process Additional diagnostics: CLSU-00100: operating system function: sclsdgcwd failed with error data: -1 CLSU-00103: error location: sclsdgcwd2 (:CLSD00183:) GGSCI (node2) 1> No obvious clues in the error message but little searching revealed that it had something to do with permissions. It was on Exadata so i tried to do a strace of ggsci and see if it could give some clues. There we go: ...

January 12, 2019 at 7:51 PM · 2 min · 254 words · Amardeep Sidhu

Failed to execute the command “”/u01/app/xag/bin/clsecho”

I was configuring GoldenGate in HA mode by following this document. Everything worked ok but in the end while running agctl config goldengate to view the configuration of GoldenGate resource, it was failing with the following error: [oracle@exadatadb02 ~]$ agctl config goldengate GG_TARGET Failed to execute the command ""/u01/app/xag/bin/clsecho" -p xag -f xag -m 5080 "GG_TARGET"" (rc=134), with the message: Oracle Clusterware infrastructure fatal error in clsecho.bin (OS PID 126367_140570897783808): Internal error (ID (:CLSB00107:)) - Error -1 (ORA-08275) determining Oracle base /u01/app/xag/bin/clsecho: line 45: 126367 Aborted (core dumped) ${CRS_HOME}/bin/clsecho.bin "$@" Failed to execute the command ""/u01/app/xag/bin/clsecho" -p xag -f xag -m 5081 "/u01/app/oragg/product"" (rc=134), with the message: If you look at the error in bold it sounds kinda obvious that it is not able to figure our where the ORACLE_BASE is. But somehow it didn’t strike me at that moment. So started looking around. If we look at the command it is running, it runs clsecho. This is simply a shell script which in turn calls $CRS_HOME/bin/clsecho.bin . In the script, it sets various environment variables and that is where the problem was. There are lines like: ...

January 8, 2019 at 10:52 PM · 2 min · 241 words · Amardeep Sidhu

dbca doesn’t list diskgroups

This is an Exadata machine running GI version 18.3.0.0.180717 and DB version 12.1.0.2.180717. On one of the DB nodes while running dbca, it doesn’t list the diskgroups. it works fine on the other node. I cheked the dbca trace and found that the kfod command was failing. I tried to run it manually and got the same error: [oracle@exadb01 ~]$ /u01/app/18.0.0.0/grid/bin/kfod op=groups verbose=true KFOD-00300: OCI error [-1] [OCI error] [Could not fetch details] [-105777048] KFOD-00105: Could not open pfile 'init@.ora' [oracle@exadb01 ~]$ I ran it with strace then: ...

December 26, 2018 at 9:01 PM · 2 min · 410 words · Amardeep Sidhu

New web based OEDA for Exadata

It started with an xls sheet (that was called dbm configurator) . Then OEDA (Oracle Exadata Deployment Assistant) was introduced that was a Java based GUI tool to enter all the information needed to configure an Exadata machine. Now with the latest patch released in Oct, OEDA has changed again; to become a web based tool. It is deployed on WebLogic and comes with some new features as well. SuperCluster deployments will continue to use the Java based OEDA tool. The new interface has support for Exadata, ZDLRA and ExaCC. It is backward compatible and can import the XMLs generated by older versions of OEDA. Some of the new features include the ability to configure single instance homes, create more than 2 diskgroups, create more than 1 database homes and databases, allow ILOMs to have a different subnet etc. ...

November 21, 2018 at 2:47 PM · 2 min · 219 words · Amardeep Sidhu

Garbled display while running FMW installer on Linux

A colleague faced this while running FMW installer on a Linux machine. The display appeared like this This thread gave a clue that it could have something to do with fonts. So I checked what all fonts related stuff was installed. [bash][root@someserver ~]# rpm -aq |grep -i font stix-fonts-1.1.0-5.el7.noarch xorg-x11-font-utils-7.5-20.el7.x86_64 xorg-x11-fonts-cyrillic-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-1-75dpi-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-9-100dpi-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-9-75dpi-7.5-9.el7.noarch libXfont-1.5.2-1.el7.x86_64 xorg-x11-fonts-ISO8859-14-100dpi-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-1-100dpi-7.5-9.el7.noarch xorg-x11-fonts-75dpi-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-2-100dpi-7.5-9.el7.noarch libfontenc-1.1.3-3.el7.x86_64 xorg-x11-fonts-ethiopic-7.5-9.el7.noarch xorg-x11-fonts-100dpi-7.5-9.el7.noarch xorg-x11-fonts-misc-7.5-9.el7.noarch fontpackages-filesystem-1.44-8.el7.noarch fontconfig-2.10.95-11.el7.x86_64 xorg-x11-fonts-ISO8859-2-75dpi-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-14-75dpi-7.5-9.el7.noarch xorg-x11-fonts-Type1-7.5-9.el7.noarch xorg-x11-fonts-ISO8859-15-75dpi-7.5-9.el7.noarch [root@someserver ~]#[/bash] ...

November 18, 2017 at 4:26 PM · 1 min · 97 words · Amardeep Sidhu

root.sh fails with CRS-2101:The OLR was formatted using version 3

Got this while trying to install 11.2.0.4 RAC on Redhat Linux 7.2. root.sh fails with a message like [sql]ohasd failed to start Failed to start the Clusterware. Last 20 lines of the alert log follow: 2017-11-09 15:43:37.883: [client(37246)]CRS-2101:The OLR was formatted using version 3.[/sql] This is bug 18370031. Need to apply the patch before running root.sh.

November 18, 2017 at 4:03 PM · 1 min · 56 words · Amardeep Sidhu

Presenting at Cloud day event of North India Chapter of AIOUG

I will be presenting a session titled “An 18 pointers guide to setting up an Exadata machine” at Cloud Day being organized by North India chapter of AIOUG. Vivek Sharma is doing multiple sessions on various cloud and performance related topics. You can register for the event here https://www.meraevents.com/event/aioug-nic-cloud-day

November 6, 2017 at 5:17 PM · 1 min · 49 words · Amardeep Sidhu

ksplice kernel updates and Exadata patching

If you have installed some one off ksplice fix for kernel on Exadata, remember to uninstall it before you do a kernel upgrade eg regular Exadata patching. As such fixes are kernel version specific so they may not work with the newer version of the kernel.

November 5, 2017 at 11:02 PM · 1 min · 46 words · Amardeep Sidhu

ORA-15040 ORA-15042 with EXTERNAL redundancy Diskgroup

A colleague was working on an ASM issue (Standalone one, Version 11.2.0.3 on AIX) at one of the customer sites. Later on, I also joined him. The issue was that the customer added few news disks to an existing diskgroup. Everything went well and the rebalance kicked in. After some time, something happened and all of a sudden the diskgroup was dismounted. While trying the mount the diskgroup again, it was giving ...

November 3, 2017 at 11:27 PM · 4 min · 715 words · Amardeep Sidhu