ERROR in the console when creating tables in Oracle during the 1st launch
ediseo Dec 5, 2012 11:43 PMHi,
I'm shifting my app from JBoss 6 to JBoss 7. But during the the 1st launch, when JPA using hibernate to creating tables, I'm getting the error as below:
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-4) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-1) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-5) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-6) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-3) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-8) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-2) HHH000262: Table not found: T_BMSC_EVENT
10:59:13,170 INFO [java.sql.DatabaseMetaData] (MSC service thread 1-7) HHH000262: Table not found: T_BMSC_EVENT
10:59:14,667 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-5) HHH000388: Unsuccessful: create table T_BMSC_EVENT (id number(19,0) not null, CONTENT_GROUP_ID number(19,0), CONTENT_URI varchar2(255 char), DELIVERY_INSTANCE_ID number(19,0), DELIVERY_SESSION_ID number(19,0), DESCRIPTION varchar2(255 char), EMBMS_SESSION_ID number(19,0), EXTENSION varchar2(255 char), MD5_VALUE varchar2(255 char), NOTIFICATION_TYPE varchar2(255 char) not null, RETRY_START_TIME timestamp not null, RETRY_TIMES number(10,0) not null, RETRY_UPDATE_TIME timestamp not null, primary key (id))
10:59:14,667 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-6) HHH000388: Unsuccessful: create table T_BMSC_EVENT (id number(19,0) not null, CONTENT_GROUP_ID number(19,0), CONTENT_URI varchar2(255 char), DELIVERY_INSTANCE_ID number(19,0), DELIVERY_SESSION_ID number(19,0), DESCRIPTION varchar2(255 char), EMBMS_SESSION_ID number(19,0), EXTENSION varchar2(255 char), MD5_VALUE varchar2(255 char), NOTIFICATION_TYPE varchar2(255 char) not null, RETRY_START_TIME timestamp not null, RETRY_TIMES number(10,0) not null, RETRY_UPDATE_TIME timestamp not null, primary key (id))
10:59:14,667 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-3) HHH000388: Unsuccessful: create table T_BMSC_EVENT (id number(19,0) not null, CONTENT_GROUP_ID number(19,0), CONTENT_URI varchar2(255 char), DELIVERY_INSTANCE_ID number(19,0), DELIVERY_SESSION_ID number(19,0), DESCRIPTION varchar2(255 char), EMBMS_SESSION_ID number(19,0), EXTENSION varchar2(255 char), MD5_VALUE varchar2(255 char), NOTIFICATION_TYPE varchar2(255 char) not null, RETRY_START_TIME timestamp not null, RETRY_TIMES number(10,0) not null, RETRY_UPDATE_TIME timestamp not null, primary key (id))
10:59:14,667 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-4) HHH000388: Unsuccessful: create table T_BMSC_EVENT (id number(19,0) not null, CONTENT_GROUP_ID number(19,0), CONTENT_URI varchar2(255 char), DELIVERY_INSTANCE_ID number(19,0), DELIVERY_SESSION_ID number(19,0), DESCRIPTION varchar2(255 char), EMBMS_SESSION_ID number(19,0), EXTENSION varchar2(255 char), MD5_VALUE varchar2(255 char), NOTIFICATION_TYPE varchar2(255 char) not null, RETRY_START_TIME timestamp not null, RETRY_TIMES number(10,0) not null, RETRY_UPDATE_TIME timestamp not null, primary key (id))
10:59:14,683 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-3) ORA-00955: name is already used by an existing object
10:59:14,667 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-6) ORA-00955: name is already used by an existing object
10:59:15,104 INFO [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-1) HHH000232: Schema update complete
It seems there're object exist conflict when some threads trying to create tables.
But actually, the database is a newly created schema.
And it's really strange that there's no trace information coming right after the "Unsuccessful:..." log, even I update the log level to DEBUG or TRACE.
Although there're so many ERRORs, the tables are created anyway.
And I noticed that the thread MSC service thread 1-1 never comes the ERROR.
I'm confused on this problem.
It seems other threads are impacted by the result of the 1st thread MSC service thread 1-1.
To verify this guess, I'd like to change the total number of MSC service thread to 1 if possible.
Could anyone help me on this problem?
1. How to change the max thread number of MSC service?
2. Why do those ERRORs come?
Thanks,