Posts Tagged ‘Oracle’

ORA-28014: Cannot Drop Administrative Users

December 2nd, 2019, posted in Oracle Queries
Share

ORA-28014: cannot drop administrative users

 

The below error is encountered when I was trying to drop schema from 12C database :atabase, dba imam, dba immam, Imam Dba, ORA-28014: Cannot Drop Administrative Users, Oracle, Oracle DBA, oracle quries

SQL> drop user BKP CASCADE;
drop user BKP CASCADE
*
ERROR at line 1:
ORA-28014: cannot drop administrative users

Solution :
SQL> alter session set "_oracle_script"=true;

Session altered.

SQL> drop user BKP CASCADE;
User dropped.
Share

DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled

November 24th, 2019, posted in Oracle Queries
Share

Customer Recommended Datapump Export (expdp) Raises Warnings Like “DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled” (Doc ID 1638799.1)

APPLIES TO :
Oracle Database – Enterprise Edition – Version 11.2.0.4 and later
Oracle Database Cloud Schema Service – Version N/A and later
Oracle Database Exadata Express Cloud Service – Version N/A and later
Oracle Database Exadata Cloud Machine – Version N/A and later
Oracle Cloud Infrastructure – Database Service – Version N/A and later
Information in this document applies to any platform.oracle immam dba,oracle, immam dba,dba imam,dba immam

SYMPTOMS :
Expdp on Oracle Standard Edition / Standard Edition 1 produces below warnings

DBMS_AW_EXP: SYS.AW$EXPRESS: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWMD: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWCREATE: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWCREATE10G: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWXML: OLAP not enabled
DBMS_AW_EXP: SYS.AW$AWREPORT: OLAP not enabled

CAUSE :
The issue was explained in
Bug 17718899 – EXPDP ON STANDARD EDITION ONE SHOWS MESSAGES “OLAP NOT ENABLED”
closed with status ‘Not a Bug’ with below comment:

OLAP is not available in Standard Edition One (SE1) or Standard Edition (SE) as per the Database Licensing Information document,
it is only available in Enterprise Edition (EE).

This message is intentionally output for DATAPUMP and coded as such in 11.2.0.4 and higher Standard Edition One (SE1) or Standard Edition (SE).

From the Datapump perspective these are warnings and it is safe to ignore them.

NOTE :
The same symptoms can be encountered with the Oracle Enterprise Edition when OLAP is not installed.

SOLUTION :
The OLAP related warnings can be safely ignored for DataPump usage.


REFERENCES :
BUG:17718899 – EXPDP ON STANDARD EDITION ONE SHOWS MESSAGES “OLAP NOT ENABLED”

Share

Show Faulted Hardware in ILOM

August 5th, 2019, posted in Solaris
Share

in an ILOM (Integrated Lights Out Manager). On this page I will use the example of a chassis fan module error. If you follow my notes and the error clears Then you didn’t have a real issue. On the other hand, If after following my notes you can’t clear the error. Then you have a real hardware issue. You can’t clear errors if the error is still an issue.

This is how you login to the command line interface for the ILOM.

 

man@earth> ssh root@ilom


The command below is one way to show system faults. The only target you should see is shell. If you see anything other then shell it is a fault. In the example below, the ILOM shows a bad system fan. Shown as 0 (/SYS/FMO).

 

–> show /SP/faultmgmt

/SP/faultmgmt
Targets:
shell
0 (/SYS/FM0)

Properties:

Commands:
cd
show


Using the show faulty command is anther way to see the system faults. This command shows a lot more detail. If you have a support contract with Oracle, you will want to paste the output of this command into the ticket, you submit to MOS. The show faulty command can be used without any paths, which will be extra useful if are coming in from a chassis ILOM.

 

–> show faulty
Target                    | Property                   | Value
———————–+————————–+———————————
/SP/faultmgmt/0    | fru                            | /SYS/FM0
/SP/faultmgmt/0/   | class                         | fault.chassis.device.fan.fail
faults/0                  |                                  |
/SP/faultmgmt/0/   | sunw-msg-id            | SPX86-8X00-33
faults/0                  |                                  |
/SP/faultmgmt/0/   | component               | /SYS/FM0
faults/0                   |                                 |
/SP/faultmgmt/0/   | uuid                          | 8692c3e4-G481-635e-f8e2-f3f215d1
faults/0                   |                                 | 13f0
/SP/faultmgmt/0/   | timestamp                | 2013-10-02/12:10:43
faults/0                   |                                 |
/SP/faultmgmt/0/   | detector                   | /SYS/FM0/ERR
faults/0                   |                                  |
/SP/faultmgmt/0/   | product_serial_number | 1203FMM107
faults/0                   |                                  |

The command below shows the event log, which will also contain the system hardware errors.

 

–> show /SP/logs/event/list


To clear the hardware fault from the logs run the command below.

 

–> show /SP/logs/event/ clear=true


Run this command to clear the fan error.

 

–> set /SYS/FM0 clear_fault_action=true

Try to clear the hardware fault. If the hardware is really having an issue, the hardware fault will come back. In about a minute or less. If you can’t clear the error and you have a support contract then this is when you summit your ticket.

If you have any questions or I missed something let me know.

Share

12c AdminServer 12.1.3 not starting and ending with error Critical WebLogicServer BEA-000386 Server subsystem failed. Reason: A MultiException has 6 exceptions

December 18th, 2018, posted in Oracle
Share

Symptom:

A MultiException has 6 exceptions. They are:

1. java.lang.AssertionError: Cannot export non clusterable object with jndiName:weblogic.jndi.internal.RootNamingNode@69f01d6c:
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.jndi.internal.RemoteNamingService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.management.mbeanservers.runtime.internal.RuntimeServerService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.mbeanservers.runtime.internal.RuntimeServerService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cacheprovider.CacheProviderServerService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cacheprovider.CacheProviderServerService

 

Cause:

This issue is caused by entry of the following JAVA_OPTIONS parameter ‘-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory’ when deploying into WebLolgic 12c. In WebLogic 12c, the built-in WebLogic Server XML Input factory implementation class is com.ctc.wstx.stax.WstxInputFactory, and the XML Factory Input should be set to this value. Due to a documentation bug, the manual deployment guide for P6 is still referencing the 11g implementation class, causing the reported issue to occur.

 

Fix:

Edit setDomainEnv.sh

 

Locate the line:

JAVA_OPTIONS at the end (added by the installer)

 

Change it to:

export JAVA_OPTIONS=”-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 -Doracle.jdbc.V8Compatible=true ${JAVA_OPTIONS}”

 

Reference Doc:

MOS Document ID: WebLogic 12c Managed Server Fails To Start When Passing The “-Djavax.xml.stream.XMLInputFactory=weblogic.xml.stax.XMLStreamInputFactory” Java Argument (Doc ID 2003152.1)

 

Share

Table That Stores Cached Queries

November 14th, 2018, posted in Oracle Queries
Share

This error is caused by corruptions that have crept into a table that stores cached queries. The only thing to do in this situation is to delete that table and clear cache by bouncing the Apache server.

There is patch available that can reduce the chance of these corruptions from happening in the future.

Please do the following

CREATE TABLE fnd_lov_choice_values_bak AS
SELECT * FROM fnd_lov_choice_values
;

DELETE fnd_lov_choice_values;

COMMIT;

Clear the cache

Then bounce the Apache server.

Then please download and apply patch Patch:9527712:R12.FWK.B

Afterwords, please try you test again.

Share