Month: September 2021

Oracle BI Server ‘obis1’ Status DOWN After OMS Upgrade

We just upgraded OMS from 13.2 to 13.4, and found an Oracle BI Server target ‘obis1’ is listed as a part of the GCDomain, and it is shown with status DOWN in EM Console.

CAUSE

It is a bug. The target ‘obis1’, shown with Down status, is a an unwanted target that got introduced as part of the upgrade to Version 13.4.

SOLUTION

Ignore the target or just delete it using EMCLI.

$ emcli login -username=sysman

$ emcli sync

$ emcli modify_target -name="/GCDomain_GCDomain/GCDomain/obis1" -type="oracle_bi_server" -properties="DisabledTargetTypes:oracle_bi_server"
Target "/GCDomain_GCDomain/GCDomain/obis1:oracle_bi_server" modified successfully

OR just delete this target.

$ emcli delete_target -name="/GCDomain_GCDomain/GCDomain/obis1" -type="oracle_bi_server"
Target "/GCDomain_GCDomain/GCDomain/obis1:oracle_bi_server" deleted successfully

ORA-39126 ORA-22990 from Data Pump

The following errors appear from ExaCC Oracle 12.1.0.2 data pump impdp:

...
..
.
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, NVL(value_n, 0), grantor, object_row, object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_level, object_int_oid, metadata_io, option_tag FROM "IMP_USER"."SYS_IMPORT_SCHEMA_01" WHERE  process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_order]
ORA-22990: LOB locators cannot span transactions

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 11259

----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0x4d745c700     27118  package body SYS.KUPW$WORKER
0x4d745c700     11286  package body SYS.KUPW$WORKER
0x4d745c700      4745  package body SYS.KUPW$WORKER
0x4d745c700     12063  package body SYS.KUPW$WORKER
0x4d745c700      2081  package body SYS.KUPW$WORKER
0x4dd854618         2  anonymous block

In procedure CREATE_MSG
KUPV$FT.MESSAGE_TEXT
KUPV$FT.MESSAGE_TEXT
In procedure SEND_MSG. Fatal=0
KUPC$QUEUE_INT.SEND
KUPC$QUEUE_INT.SEND
Processing object type SCHEMA_EXPORT/TABLE/TABLE
KUPF$FILE.CLOSE_CONTEXT
KUPF$FILE.CLOSE_CONTEXT
In procedure DETERMINE_FATAL_ERROR with ORA-22990: LOB locators cannot span transactions
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "HR"."EMPLOYEE"              751.6 KB    3371 rows
. . imported "HR"."SALARY"                1.412 MB    2992 rows
...
..
.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

ORA-65025 when Renaming Global_Name in PDB

SQL>select * from global_name;

GLOBAL_NAME
--------------------------------------------------
OLDNAME

SQL>  alter pluggable database rename global_name to NEWNAME;
 alter pluggable database rename global_name to NEWNAME
                                                *
ERROR at line 1:
ORA-65045: pluggable database not in a restricted mode

SOLUTION

Open PDB in restricted mode, and close all other instances in RAC environment.

SQL> alter pluggable database OLDNAME open restricted;

Pluggable database altered.

SQL> alter session set container=OLDNAME;

Session altered.

SQL>alter pluggable database rename global_name to NEWNAME;

Pluggable database altered

SQL>select * from global_name;

GLOBAL_NAME
--------------------------------------------------
NEWNAME