留言板
HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
petar banicevic,修改在15 年前。
HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
Junior Member 帖子: 73 加入日期: 08-5-27 最近的帖子
QUESTION:
What mean these warnings and can I ignore them?
Can I fix them ???
Thank you
PS:
I created database on db2 with UTF-8 codeset
==================================
(e.g. CREATE DATABASE LPORTAL ON 'C:' USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM; )
And when launching portal I get following messages:
==================================
Starting Liferay Enterprise Portal 5.0.1 (Luther / Build 5001 / April 14, 2008)
22:12:56,484 INFO [DynamicDialect:80] Determining dialect for DB2/NT 8
22:12:56,500 INFO [DynamicDialect:106] Using dialect org.hibernate.dialect.DB2Dialect
22:12:58,125 INFO [PortalImpl:184] Portal lib url /C:/Program Files/liferay-portal-tomcat-6.0-5.0.1/webapps/ROOT/WEB-IN
F/lib/portal-impl.jar!/com/liferay/portal/util/PortalImpl.class
22:12:58,125 INFO [PortalImpl:209] Portal lib directory /C:/Program Files/liferay-portal-tomcat-6.0-5.0.1/webapps/ROOT/
WEB-INF/lib/
22:13:02,609 WARN [ReleaseLocalServiceImpl:83] DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DB2ADMIN.RELEASE_
22:13:02,609 INFO [ReleaseLocalServiceImpl:96] Create tables and populate with default data
22:13:07,281 WARN [DBUtil:365] DB2 SQL error: SQLCODE: -614, SQLSTATE: 54008, SQLERRMC: IX_7020130F
22:13:08,250 INFO [StartupAction:203] Running verification com.liferay.portal.verify.VerifyProcessSuite
22:13:08,250 INFO [VerifyProcessSuite:37] Verifying
22:13:08,250 INFO [VerifyProperties:40] Verifying
22:13:08,250 INFO [VerifyLucene:39] Verifying
22:13:08,250 INFO [VerifyCounter:44] Verifying
22:13:08,265 INFO [VerifyOracle:52] Verifying
22:13:08,281 INFO [VerifyBlogs:42] Verifying
22:13:08,281 INFO [CustomSQLUtil:110] Database name DB2/NT
22:13:08,281 INFO [CustomSQLUtil:119] Detected DB2 with database name DB2/NT
22:13:08,500 INFO [VerifyBookmarks:42] Verifying
22:13:08,515 INFO [VerifyDocumentLibrary:42] Verifying
22:13:08,515 INFO [VerifyGroup:46] Verifying
22:13:08,515 INFO [VerifyImageGallery:42] Verifying
22:13:08,531 INFO [VerifyJournal:57] Verifying
22:13:08,546 INFO [VerifyLayout:43] Verifying
22:13:08,546 INFO [VerifyMessageBoards:42] Verifying
22:13:08,562 INFO [VerifyUser:44] Verifying
22:13:08,562 INFO [VerifyWiki:42] Verifying
22:13:08,578 INFO [StartupAction:210] Finished verification com.liferay.portal.verify.VerifyProcessSuite
22:13:09,125 INFO [HotDeployUtil:76] Initializing hot deploy manager 180619972
22:13:09,125 INFO [ServerDetector:76] Detected server tomcat
22:13:09,375 INFO [AutoDeployDir:76] Auto deploy scanner started for C:\Documents and Settings\Administrator\liferay\de
TWO WARNINGS
==================================
WARN [ReleaseLocalServiceImpl:83] DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DB2ADMIN.RELEASE_
WARN [DBUtil:365] DB2 SQL error: SQLCODE: -614, SQLSTATE: 54008, SQLERRMC: IX_7020130F
I have googled and have found this description for the first warning:
==================================
"If the userid you are using is db2admin, and you don't supply a high level
qualifier on the table name, the DB2 assumes that DB2ADMIN is the qualifier
(schema) name. You can use the SET SCHEMA statement before hand, use an
alias, or use the a userid with the same name as your schema."
QUESTION
==================================
Does this explanation describe my problem as well ? What can I do?
What mean these warnings and can I ignore them?
Can I fix them ???
Thank you
PS:
I created database on db2 with UTF-8 codeset
==================================
(e.g. CREATE DATABASE LPORTAL ON 'C:' USING CODESET UTF-8 TERRITORY US COLLATE USING SYSTEM; )
And when launching portal I get following messages:
==================================
Starting Liferay Enterprise Portal 5.0.1 (Luther / Build 5001 / April 14, 2008)
22:12:56,484 INFO [DynamicDialect:80] Determining dialect for DB2/NT 8
22:12:56,500 INFO [DynamicDialect:106] Using dialect org.hibernate.dialect.DB2Dialect
22:12:58,125 INFO [PortalImpl:184] Portal lib url /C:/Program Files/liferay-portal-tomcat-6.0-5.0.1/webapps/ROOT/WEB-IN
F/lib/portal-impl.jar!/com/liferay/portal/util/PortalImpl.class
22:12:58,125 INFO [PortalImpl:209] Portal lib directory /C:/Program Files/liferay-portal-tomcat-6.0-5.0.1/webapps/ROOT/
WEB-INF/lib/
22:13:02,609 WARN [ReleaseLocalServiceImpl:83] DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DB2ADMIN.RELEASE_
22:13:02,609 INFO [ReleaseLocalServiceImpl:96] Create tables and populate with default data
22:13:07,281 WARN [DBUtil:365] DB2 SQL error: SQLCODE: -614, SQLSTATE: 54008, SQLERRMC: IX_7020130F
22:13:08,250 INFO [StartupAction:203] Running verification com.liferay.portal.verify.VerifyProcessSuite
22:13:08,250 INFO [VerifyProcessSuite:37] Verifying
22:13:08,250 INFO [VerifyProperties:40] Verifying
22:13:08,250 INFO [VerifyLucene:39] Verifying
22:13:08,250 INFO [VerifyCounter:44] Verifying
22:13:08,265 INFO [VerifyOracle:52] Verifying
22:13:08,281 INFO [VerifyBlogs:42] Verifying
22:13:08,281 INFO [CustomSQLUtil:110] Database name DB2/NT
22:13:08,281 INFO [CustomSQLUtil:119] Detected DB2 with database name DB2/NT
22:13:08,500 INFO [VerifyBookmarks:42] Verifying
22:13:08,515 INFO [VerifyDocumentLibrary:42] Verifying
22:13:08,515 INFO [VerifyGroup:46] Verifying
22:13:08,515 INFO [VerifyImageGallery:42] Verifying
22:13:08,531 INFO [VerifyJournal:57] Verifying
22:13:08,546 INFO [VerifyLayout:43] Verifying
22:13:08,546 INFO [VerifyMessageBoards:42] Verifying
22:13:08,562 INFO [VerifyUser:44] Verifying
22:13:08,562 INFO [VerifyWiki:42] Verifying
22:13:08,578 INFO [StartupAction:210] Finished verification com.liferay.portal.verify.VerifyProcessSuite
22:13:09,125 INFO [HotDeployUtil:76] Initializing hot deploy manager 180619972
22:13:09,125 INFO [ServerDetector:76] Detected server tomcat
22:13:09,375 INFO [AutoDeployDir:76] Auto deploy scanner started for C:\Documents and Settings\Administrator\liferay\de
TWO WARNINGS
==================================
WARN [ReleaseLocalServiceImpl:83] DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DB2ADMIN.RELEASE_
WARN [DBUtil:365] DB2 SQL error: SQLCODE: -614, SQLSTATE: 54008, SQLERRMC: IX_7020130F
I have googled and have found this description for the first warning:
==================================
"If the userid you are using is db2admin, and you don't supply a high level
qualifier on the table name, the DB2 assumes that DB2ADMIN is the qualifier
(schema) name. You can use the SET SCHEMA statement before hand, use an
alias, or use the a userid with the same name as your schema."
QUESTION
==================================
Does this explanation describe my problem as well ? What can I do?
petar banicevic,修改在15 年前。
RE: HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
Junior Member 帖子: 73 加入日期: 08-5-27 最近的帖子
When the tables are created using script then this problem is not present. You should not let liferay to create tables.
Namrata Hangal,修改在11 年前。
RE: HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
Regular Member 帖子: 161 加入日期: 10-7-27 最近的帖子When the tables are created using script then this problem is not present
Where can I find this script?
Boris Yurkevich,修改在11 年前。
RE: HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
New Member 帖子: 8 加入日期: 12-4-20 最近的帖子
Namrata Hangal,
Are you found the script so far? I'm particularly looking for DB2 10.1 on Windows 7 + Liferay 6 and DB2 10.1 on OS X + Liferay 6.
Are you found the script so far? I'm particularly looking for DB2 10.1 on Windows 7 + Liferay 6 and DB2 10.1 on OS X + Liferay 6.
Hitoshi Ozawa,修改在11 年前。
RE: HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
Liferay Legend 帖子: 7942 加入日期: 10-3-24 最近的帖子
Just download liferay's source code. SQL scripts are under the sql directory.
Henri Charles,修改在7 年前。
RE: HELP:DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704
New Member 发布: 1 加入日期: 16-7-15 最近的帖子
In order to fix your DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, you can check out the help section here – https://www.ibm.com/support/knowledgecenter/SSEPEK_10.0.0/codes/src/tpc/n219.html
If the above solution does not help you to fix the errors then you can try the third party tool popularly known as DB2 file Repair Tool.
Hope this could help you.
If the above solution does not help you to fix the errors then you can try the third party tool popularly known as DB2 file Repair Tool.
Hope this could help you.