AnsweredAssumed Answered

Found invalid object(s) in the database.

Question asked by Amit Khatua on Apr 24, 2017
Latest reply on Apr 28, 2017 by Amit Khatua

Hi, 

 

Any idea why this error occurs and the resolution please. The ADC was taking a huge time and we restarted the aveksa_server service. Got this error and stuck.

Version - 7.0.2 with local database

 

log details - 

 

04/24/2017 16:02:02.815 INFO (MSC service thread 1-2) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization Start ********************
04/24/2017 16:02:05.818 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Java version: 1.7.0_111
04/24/2017 16:02:05.819 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Java VM version: 24.111-b01
04/24/2017 16:02:05.819 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Java heap init: 120M
04/24/2017 16:02:05.822 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Java heap used: 252M
04/24/2017 16:02:05.822 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Java heap max: 989M
04/24/2017 16:02:05.823 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Memory options: -Xmx1024m -XX:MaxPermSize=256M
04/24/2017 16:02:05.825 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Operating System: Linux
04/24/2017 16:02:05.825 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Operating System Architecture: amd64
04/24/2017 16:02:05.825 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Operating System Version: 3.0.76-0.11-default
04/24/2017 16:02:05.842 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] JDBC driver: 12.1.0.2.0
04/24/2017 16:02:05.848 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Oracle version: 12.1.0.2
04/24/2017 16:02:07.004 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Schema user: AVUSER
04/24/2017 16:02:07.005 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Reporting engine user: AVDWUSER
04/24/2017 16:02:07.009 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Public database schema user: ACMDB
04/24/2017 16:02:07.018 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Tablespace information
04/24/2017 16:02:07.018 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] DATA 256K Tablespace :DATA_256K
04/24/2017 16:02:07.018 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] DATA 1M Tablespace :DATA_1M
04/24/2017 16:02:07.021 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] DATA 25M Tablespace :DATA_25M
04/24/2017 16:02:07.021 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] DATA 50M Tablespace :DATA_50M
04/24/2017 16:02:07.024 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] INDEX 256K Tablespace :INDX_256K
04/24/2017 16:02:07.024 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] INDEX 1M Tablespace :INDX_1M
04/24/2017 16:02:07.025 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] INDEX 25M Tablespace :INDX_25M
04/24/2017 16:02:07.025 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] INDEX 50M Tablespace :INDX_50M
04/24/2017 16:02:07.049 INFO (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Could not determine the incoming patch number. This could be due to missing patch meta file
04/24/2017 16:02:07.072 INFO (MSC service thread 1-2) [SystemOut] executing Create Scripts/Recompile_report_user_objects.sql
04/24/2017 16:02:07.136 INFO (MSC service thread 1-2) [SystemOut] The log is available at: /home/oracle/wildfly/standalone/log/reporting-user-synonyms.log
04/24/2017 16:02:07.600 ERROR (MSC service thread 1-2) [com.aveksa.migration.jdbctool.CheckDatabase] Found invalid object(s) in the database. Please check the log for error(s).
04/24/2017 16:02:07.700 INFO (MSC service thread 1-2) [com.aveksa.server.runtime.AveksaSystem] ******************** Aveksa System Initialization End ********************
04/24/2017 16:02:07.702 FATAL (MSC service thread 1-2) [com.aveksa.server.runtime.AveksaSystem]

****************************************

Initialization has failed!

Found invalid object(s) in the database. Please check the log for error(s).


****************************************

UI - 

 

Outcomes