Re: Help installing CCM/CMS 6.1
Tuan Nguyen <[email protected]> Wed, 05 May 2004 17:21:52 -0400
| Newsgroups | gmane.linux.redhat.ccm.general |
|---|---|
| Message-ID | <[email protected]> |
Thanks for the link Tom. It turned out the problem was the database user
did not have appropriate privilege, recreating the user solved the
"conflicting table" problem. However, I ran into a different problem,
see the output below:
CHECK: The database type is recognized
CHECK: The Oracle JDBC driver is available
CHECK: The ccm-core package is configured.
CHECK: The JDBC URL parameter is set.
CHECK: The database is accepting connections
CHECK: JAAS is available
WARNING: Multiple implementations of the same API found
The CCM runtime classpath contains two or more implementations of the
same API. Only one, from the first location listed below, will be
used.
/usr/local/IBMJava2-141/jre/lib/security.jar
/usr/local/IBMJava2-141/jre/lib/ext/jaas.jar
/usr/share/ccm-tools/lib/security/jaas.jar
CHECK: JCE is available
WARNING: Multiple implementations of the same API found
The CCM runtime classpath contains two or more implementations of the
same API. Only one, from the first location listed below, will be
used.
/usr/local/IBMJava2-141/jre/lib/security.jar
/usr/local/IBMJava2-141/jre/lib/ext/jce.jar
/usr/share/ccm-tools/lib/security/jce.jar
2004-05-05 17:12:16,646 [ main] INFO packaging.Loader - Loading schema
for ccm-core
2004-05-05 17:12:50,164 [ main] INFO runtime.Startup - Initializing WAF
runtime
2004-05-05 17:12:51,961 [ main] INFO runtime.Startup - Initialization
complete
2004-05-05 17:12:51,961 [ main] INFO packaging.Loader - Running
initializer com.arsdigita.core.Initializer
com/arsdigita/notification/Notification.pdl: line 34, column 10
[warning]: table already has primary key:
com/arsdigita/notification/Notification.pdl: line 32, column 4
com/arsdigita/notification/Notification.pdl: line 35, column 10
[warning]: table already has primary key:
com/arsdigita/notification/Notification.pdl: line 32, column 4
2004-05-05 17:12:55,096 [ main] ERROR rdbms.RDBMSEngine - select
t0.pdl_id as "this.id",
t6.object_type as "this.objectType",
t6.display_name as "this.displayName",
t6.default_domain_class as "this.defaultDomainClass",
t0.pdl_file as "this.pdlFile",
t0.dynamic_object_type as "this.dynamicType"
from persistence_dynamic_ot t0
join acs_objects t6 on t0.pdl_id = t6.object_id
java.sql.SQLException: ORA-00933: SQL command not properly ended
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java:1597)
at
oracle.jdbc.oci8.OCIDBAccess.parseExecuteDescribe(OCIDBAccess.java:798)
at
oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:1674)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1870)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:407)
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:489)
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:431)
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:265)
at com.redhat.persistence.Cursor.execute(Cursor.java:131)
at com.redhat.persistence.Cursor.next(Cursor.java:115)
at
com.arsdigita.persistence.DataQueryImpl.next(DataQueryImpl.java:646)
at com.arsdigita.persistence.Initializer.init(Initializer.java:59)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.core.Initializer.init(Initializer.java:69)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.runtime.Startup.run(Startup.java:219)
at com.arsdigita.packaging.Loader.loadData(Loader.java:111)
at com.arsdigita.packaging.Load.run(Load.java:348)
at com.arsdigita.packaging.MasterTool.main(MasterTool.java:91)
2004-05-05 17:12:55,099 [ main] ERROR rdbms.RDBMSEngine - []
2004-05-05 17:12:55,100 [ main] ERROR rdbms.RDBMSEngine - []
2004-05-05 17:12:55,100 [ main] ERROR rdbms.RDBMSEngine - {}
com.arsdigita.persistence.PersistenceException (root cause:
com.redhat.persistence.engine.rdbms.RDBMSEngine$4: ORA-00933: SQL
command not properly ended
)
at
com.arsdigita.persistence.PersistenceException.newInstance(PersistenceException.java:100)
at
com.arsdigita.persistence.PersistenceException.newInstance(PersistenceException.java:86)
at
com.arsdigita.persistence.DataQueryImpl.next(DataQueryImpl.java:648)
at com.arsdigita.persistence.Initializer.init(Initializer.java:59)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.core.Initializer.init(Initializer.java:69)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.runtime.Startup.run(Startup.java:219)
at com.arsdigita.packaging.Loader.loadData(Loader.java:111)
at com.arsdigita.packaging.Load.run(Load.java:348)
at com.arsdigita.packaging.MasterTool.main(MasterTool.java:91)
Root cause:
com.redhat.persistence.engine.rdbms.RDBMSEngine$4: ORA-00933: SQL
command not properly ended
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:517)
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:431)
at
com.redhat.persistence.engine.rdbms.RDBMSEngine.execute(RDBMSEngine.java:265)
at com.redhat.persistence.Cursor.execute(Cursor.java:131)
at com.redhat.persistence.Cursor.next(Cursor.java:115)
at
com.arsdigita.persistence.DataQueryImpl.next(DataQueryImpl.java:646)
at com.arsdigita.persistence.Initializer.init(Initializer.java:59)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.core.Initializer.init(Initializer.java:69)
at
com.arsdigita.runtime.CompoundInitializer.init(CompoundInitializer.java:118)
at com.arsdigita.runtime.Startup.run(Startup.java:219)
at com.arsdigita.packaging.Loader.loadData(Loader.java:111)
at com.arsdigita.packaging.Load.run(Load.java:348)
at com.arsdigita.packaging.MasterTool.main(MasterTool.java:91)
Tom Baik wrote:
> Take a look at this post and its follow-up:
> https://listman.redhat.com/archives/redhat-ccm-list/2004-March/msg00080.html.
>
> Maybe you can gleam something from it.
>
>
>
>
> --- Tuan Nguyen <[email protected]> wrote:
>
>>I forgot to mention that I am using oracle, usually dropping the user
>>
>>with cascade option will get rid of any data belonging to that user,
>>therefore I don't think that was the problem. Does anyone know how to
>>
>>get more verbose error reporting from ccm load? I tried the --verbose
>>
>>but it was unrecognized.
>>
>>Tuan.
>>
>>Tom Baik wrote:
>>
>>>You should drop the db not the user. I am assuming you're using
>>>Postgresql. "su" to the postgres user then do a "dropdb" on your
>>>database. Then create a new db.
>>>
>>>
>>>
>>>--- Tuan Nguyen <[email protected]> wrote:
>>>
>>>
>>>>Hi Tom,
>>>>
>>>>I drop the user, then recreated a new user, same result. After
>>>>running
>>>>ccm load, I checked the user's schema to see if any table was
>>
>>created
>>
>>>>and there was none. I keep getting that error regardless. Any other
>>
>>>>idea? Thanks.
>>>>
>>>>Tom Baik wrote:
>>>>
>>>>
>>>>>If you're doing a fresh install, the best thing to do is to drop
>>>>
>>>>the db
>>>>
>>>>
>>>>>and rerun "ccm load". It looks like you've run "ccm load" once
>>>>
>>>>already
>>>>
>>>>
>>>>>and your previous execution loaded some tables into your db. Your
>>>>>subsequent try is then conflicting with those previously loaded
>>>>
>>>>tables.
>>>>
>>>>
>>>>>Tom
>>>>>
>>>>>
>>>>>
>>>>>--- Tuan Nguyen <[email protected]> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I can't seem to be able to load the ccm-core package for a fresh
>>>>>>install. I keep getting the "conflicting tables: [acs_objects]"
>>>>>>error.
>>>>>>What am I doing wrong? Below is the output from running "ccm load
>>
>>>>>>--interactive ccm-core"
>>>>>>
>>>>>>
>>>>>>CHECK: The database type is recognized
>>>>>>CHECK: The Oracle JDBC driver is available
>>>>>>CHECK: The ccm-core package is configured.
>>>>>>CHECK: The JDBC URL parameter is set.
>>>>>>CHECK: The database is accepting connections
>>>>>>CHECK: JAAS is available
>>>>>>WARNING: Multiple implementations of the same API found
>>>>>>
>>>>>>The CCM runtime classpath contains two or more implementations of
>>>>
>>>>the
>>>>
>>>>
>>>>>>same API. Only one, from the first location listed below, will
>>
>>be
>>
>>>>>>used.
>>>>>>
>>>>>> /usr/local/IBMJava2-141/jre/lib/security.jar
>>>>>> /usr/local/IBMJava2-141/jre/lib/ext/jaas.jar
>>>>>> /usr/share/ccm-tools/lib/security/jaas.jar
>>>>>>CHECK: JCE is available
>>>>>>WARNING: Multiple implementations of the same API found
>>>>>>
>>>>>>The CCM runtime classpath contains two or more implementations of
>>>>
>>>>the
>>>>
>>>>
>>>>>>same API. Only one, from the first location listed below, will
>>
>>be
>>
>>>>>>used.
>>>>>>
>>>>>> /usr/local/IBMJava2-141/jre/lib/security.jar
>>>>>> /usr/local/IBMJava2-141/jre/lib/ext/jce.jar
>>>>>> /usr/share/ccm-tools/lib/security/jce.jar
>>>>>>conflicting tables: [acs_objects]
>>>>>>
>>>>>>
>>>>>>--
>>>>>>Redhat-ccm-list mailing list
>>>>>>[email protected]
>>>>>>https://www.redhat.com/mailman/listinfo/redhat-ccm-list
>>>>>>Archives: https://www.redhat.com/pipermail/redhat-ccm-list/
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>__________________________________
>>>>>Do you Yahoo!?
>>>>>Win a $20,000 Career Makeover at Yahoo! HotJobs
>>>>>http://hotjobs.sweepstakes.yahoo.com/careermakeover
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>__________________________________
>>>Do you Yahoo!?
>>>Win a $20,000 Career Makeover at Yahoo! HotJobs
>>>http://hotjobs.sweepstakes.yahoo.com/careermakeover
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Win a $20,000 Career Makeover at Yahoo! HotJobs
> http://hotjobs.sweepstakes.yahoo.com/careermakeover
--
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/