Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the problems encountered in the process of Oracle12c import and export

2025-03-31 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

This article introduces the knowledge about "how to solve the problems encountered in the process of Oracle 12c import and export". In the actual case operation process, many people will encounter such difficulties. Next, let Xiaobian lead you to learn how to deal with these situations! I hope you can read carefully and learn something!

Problems encountered during import and export and their solutions

Expdp/impdp takes too long.

Cause: Too many objects, especially partition tables

select object_type,count(*) from dba_objectswhere group by object_type;------------------------------------------------------------------table partition table subpartition index subpartition index partition------------------------------------------------------------------

II. Infinite growth of temporary table space in impdp process leads to import failure

ORA-01652: unable to extend temp segment by 128 in tablespace TEMP

After confirming with the manufacturer a bug in 12.1.0.1

This bug does not have a patch on version 12.1.0.1, and it is no longer possible to apply for a patch on version 12.1.0.1.

Impp import failed

Cause analysis:

Limpdf temporary table space, then, is generally related to index, index creation needs sorting, when the memory is not enough will use temporary table space.

Wait for unread message on broadcast channel

3. 12c new feature causes sysaux table space to continue to grow

Problem description: sysaux table space continues to grow after the application accesses the 12c database.

Related knowledge:12c Unified auditing is used to monitor database operations performed by users defined in the audit policy. 12.1.0.1, a statistical policy named ORA_SECURECONFIG exists by default.

Because the ORA_SECURECONFIG definition in version 12.1.0.1 described earlier contains LOGON and LOGOFF information, it may cause the SYSAUX table space to grow continuously.

Solution:

1. Clean up unified audit information;DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL( AUDIT_TRAIL_TYPE => DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFED) 2. Turn off the default unified audit policy. NOAUDIT POLICY ORA_SECURECONFIG;

4. Use wm_concat function on 12c

Problem Description: The wm_concat function has been discarded on 11gR2 and 12cR1 and is used in programs developed in 10g. After upgrading to 12c, the stored procedure compilation error is as follows:

java.sql.SQLSyntaxErrorException: ORA-00904: "WMSYS". "WM_CONCAT": invalid identifier

The wm_concat function differs in each version

In 10.2.0.4 / 11.1.0.7 / 11.2.0.1 it returns VARCHAR2SQL> desc wmsys.wm_concat; FUNCTION wmsys.wm_concat RETURNS VARCHAR2

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report