Skip to Main Content
Forums

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

[Database character set migration DMU 19.1] DMU is not responding after using schedule column option

Khang MaiFeb 18 2020 — edited Feb 18 2020

Hi everyone,

Issue:

  • I am facing an issue with DMU 19.1 which is the DMU application is not responding (frozen or crashed) after I cleansed the data by using schedule column the issue (the issue is over column limit). It happens frequently and whenever this occurs, I have to use the task manager to end the DMU application.

Here is my summary of the setting:

  • The DMU is installed on a Window Server 2008 R2 SP1 client machine which connects to the Oracle Database Server 11.2.0.4. The host of the database server is Linux base.
  • The JDK that DMU is currently using is JDK 1.8.0_231 
  • The DMU was installed all the packages that requires from DMU document including creating a separated tablespace for DMU repository.
  • The DMU will be used to convert the character set for a database with the size is greater than 1.5 TB storage.
  • I was able to scan the entire database and now I am in cleansing data step, and this issue happened.

Looking at the log, I was able to find the cause. Due to privacy, I could not copy all the log into here. Instead, I will try to write down the log issue as much as I can. Here is the log message:

  • Main; S; 05001 Exception call stack in Java.lang.ArrayIndexOutofBounds Exception -2 at Java.Util.ArrayList.elementData (ArrayList.Java: 422) at Java.Util.ArrayList.get (ArrayList.Java: 435) at oracle.duma.gui.cleansing.cache.defaultCachePage.getObject (defaultCachePage.Java: 96) at oracle.dmu.gui.cleansing.cache.defaultDataProvider.getCellData (defaultDataProvider.Java: 262) at oracle.duma.gui.cleansing.model.cleansingDataGridModel.getOriginalDataAt (cleansingDataGridModel.Java: 1218) ....
  • The rest of the log was exceptions throws from Java.wing and java.awt. For example. JComponent . Java 5158, 1065, 889 or Javax.swing.bufferStrategyPaintManager 290 and so on.

My attempt :

  • I think I may try to find some solutions if I read the ide.conf or dmu.conf, but I could not find much about this information or any documents on this subject.

Please, let me know what I should do or what I should analyze this issue.

Best,

Khang Mai

Comments

Post Details

Added on Feb 18 2020
#database-and-application-migrations
2 comments
685 views